17 дек. 2015 г. 11:12 пользователь "Antoine Jacoutot" <ajacou...@bsdfrog.org> написал: > > On Wed, Dec 16, 2015 at 10:33:33PM +0300, Vadim Zhukov wrote: > > (some history) > > > > During this summer the Jannis Tsaraias worked on the pkg_module, an > > automated port creation framework as a GSoC Project. The project > > succeeded, and Jannis stayed to maintain the code and accept patches > > from interested parties: > > > > https://github.com/diethyl/pkg_module > > > > (back to nowadays) > > > > A few months went, and we're still at the same place. pkg_module > > proved to work by a few people already, and should be a nice addition > > for 5.9. So I want to move on and finally import it. I'm attaching the > > archive to be extracted under /usr/ports/infrastructure. After that > > just type something like "pkg_module ruby dbf" and see how easy it > > goes. :) > > > > Personally I use it about once a month, saving a hour or two of manual > > work. In particular, I'm trying to reuse this code to make maintaining > > KDE Frameworks easier: doing things manually, I have to re-start > > porting a new version before finishing a previous one... > > > > Any comments/suggestions/objections/okays? > > I haven't looked at it yet but just one question: does it allow to *update* existing ports? > I wouldn't really be happy if it helped pushing even more orphaned ruby-* p5* ... stuffs into the tree.
Not yet, unfortunately. Dreaming of it as well as you do. :) Actually, since many autogenerated ports do not need tweaking at all, they could be updated by replacing the whole directory. The only churn will happen at $OpenBSD$ tags, but those are handled by CVS itself without problems. But the problems will arise in other ports, depending on old version and changing behaviour (up to not being to run) with new ones. I don't see simple solution here. :( -- Vadim Zhukov
