Stanislav Sinyagin wrote: > As for the packaging, the most annoing thing (only imho, I've built only > one package, much less than you folks) was setting correctly all > the path names in configure options, and then packing it all with a proper > file name. > > Did someone think of developing a simple framework for making the packages, > especially for that software which supports Cygwin and configure does everything > for you? > > something like > cygmkpkg expat-1.95.2.tar.gz > and that's it? > Let the script do all unpacking, configuring, making, then packaging > efforts? It would just prompt for the setup.ini description and category, > or take them from previous version?
Chuck did write a script that automatizes most of these steps. You can call it a framework since all his new packages uses this script (and so does mine). Take a look at one of them. There was a long discussion about packaging and package management. But we don't want to reinvent the wheel and implement a rpm-like or dpkg-like infrastructure. IIRC a decision was postponed till setup.exe could be used to bootstrap one of the already existent packaging systems. > > Then, after that, there will be no questions like "who's gonna maintain > this package?" -- even the checkup for the sources version update can be > automated. > > As for NASM, I've seen only one program which uses it (and can compile > without it too) -- that's Lame. Are there more? Perhaps, some hardware > related tools, like CD-R burning? Video processing? > > Cheers, > Stan > > __________________________________________________ > Do You Yahoo!? > Yahoo! Sports - live college hoops coverage > http://sports.yahoo.com/ -- Med venlig hilsen / Kind regards Hack Kampbjørn