On Wed, Dec 08, 2010 at 11:25:35AM +0100, Exceed <[email protected]> wrote: > 1) Latest version could be a tar.gz or a tar.bz2 in "simple projects", > respecting submission order, so _F_sourceforge_ext becomes a russian > roulette
As long as it's .tar.gz or .tar.bz2 Flasttar handles that. :) > 2) On complex projects (lib+app), no way : dev could update lib and app, > or app and lib, latest version will move from lib to app, and chkworld > will become crazy... One common pattern: that is always about: 1) There is a main project (libexif) 2) There is a subproject (exif) 3) Each release has its own subdir. So maybe we could add an _F_sourceforge_complex="libexif/exif" and use the below hack instead of Flasttar in those cases. Does it sound OK? > Please have a look on some of my packages to feel these points : > - Point 1 - xapps-extra/qmc2 : http://sourceforge.net/projects/qmc2/files up2date="lynx -dump http://sourceforge.net/projects/qmc2/files/qmc2/|grep 'http.*qmc2/.*qmc2/.*/$'|sed 's|.*/\(.*\)/|\1|;q'" > - Point 2 (+ point 1) - apps-extra/exif : > http://sourceforge.net/projects/libexif/files/exif/ (I know you like > this one ^^) lynx -dump http://sourceforge.net/projects/libexif/files/exif/|grep 'http.*libexif/.*exif/.*/$'|sed 's|.*/\(.*\)/|\1|;q'
pgpwzdPdBf9L1.pgp
Description: PGP signature
_______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
