The issue has been reported and will be fixed soon.
]]>I'm back in the maintainer/lead developer seat.
]]>Configuration is kept in ~/.paktahn/config.lisp. All other files produced and kept by Paktahn are in this directory as well. You can modify pretty much every aspect of Paktahn's logic in config.lisp, but for end-users the only useful options are about setting the color scheme and debug level.
Right now packages built by Paktahn are deleted after installation. It would be easy to add functionality to keep around packages if this is important for you. In this case please open a feature request here: https://github.com/skypher/paktahn/issues
]]>Thanks for your patience and sorry for my delay, folks.
An x86_64 binary is available under http://redlinernotes.com/docs/ as usual.
]]>I skimmed the patch and it looks good. At work now but I'll merge it, bump the version and cut a release in the next 6-8 hours.
]]> ==> Continue building youtube-viewer? (y/n/R) y
Dependency: git is up to date.
Dependency: perl-libwww is up to date.
resolving dependencies...
looking for inter-conflicts...
:: mplayer and mplayer-vdpau-svn are in conflict. Remove mplayer-vdpau-svn? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: mplayer and mplayer-vdpau-svn are in conflict
Please let me know if you need other information about this.
]]>x86_64 binary is in the usual spot, 32bit is hopefully soon to follow: http://redlinernotes.com/docs/paktahn-0 … pkg.tar.xz
Though this may seem a small release and these only a few features, a lot of internal refactoring has been going on. As I'm more settled into my first programming job, I want my entire focus for the next release to be getting a sound test suite going and then cleaning up the internals as much as possible. This will facilitate more painless work going forward from Trevis and I and also make it easier for others to dip their toes in without worrying about breaking things.
Plans for the next release are already shaping up as follows:
* Trevis will work on pak -U / LocalPackageSupport. Some progress was already made in this direction in a fork on github some time back but will need integration and cleanup.
* Any commands pacman supports that we don't sensibly fall back on or integrate with at this time (for example, pacman -Si) will be supported.
* I will be working on a test suite followed by lots of refactoring, internal documentation and cleanup.
Anybody want to make paktahn a proper website as we get closer to 1.0?
As always, thanks for keeping the bug reports, feature ideas and feedback flowing. I really appreciate it! One final note: I'm spending a good amount of time hanging out in #paktahn on Freenode and Trevis pops through a bit as well. Sometimes I'm sleeping or working but I have a bouncer so I don't miss anything. Feel free to swing by and drop me a line!
Cheers,
Brit
Trevis has been putting in some good work on Paktahn of late. In particular, a lot of work was spent fixing our support for provider packages to detect when a providing package has been installed from AUR. I'm hoping to make a new release (0.9.6) on September the 10th. Hopefully I'll have a chance to put in some work and bugfixes myself by then. Thanks for keeping the bug reports and feedback coming and just generally being awesome.
Cheers,
Brit
GSF1200S,
Thanks for commenting!
1) I love this feature idea. That is absolutely something paktahn should do and it shouldn't be hard to pull off.
2) There are two issues at work here. A) Paktahn keeps a cache of what PKGBUILDs you've already seen. It md5sums each PKGBUILD and if that hash is in the cache, doesn't prompt you about it. I would be interested in how people feel about this feature. At the very least, we could easily make it optional behavior. B) Does Paktahn prompt to review the pkgbuild before trying to install dependencies? If it doesn't, it seems reasonable to me that it should.
I would very much appreciate it if you would create issues for these on github: http://github.com/skypher/paktahn/issues
Hopefully trev311 and I can get to those issues and make a new release sometime soon.
As promised, I have created issues on Github for the above. I also included another idea in one of the issues, but that is optional and not a very big deal for me as I only run ~10 AUR packages at a time anyways. Watching the project now
]]>