On Sun, Oct 24, 2010 at 12:56 PM, Holger Freyther <[email protected]> wrote: > On 10/24/2010 08:35 PM, Khem Raj wrote: > >>> >>> this is used in all efl recipes and I've noticed it in elementary only >>> because python-elementary depends on such new version. >> >> Do you have a list of recipes which use this ? I am sure with git it >> will be hard to use such a thing >> as the git revs are random and simlarily many other SCMs > > > Speaking as upstream co-author of OpenBSC. We are using something like this to > get the revision from the last tag of the repository. If someone is doing a > make dist(check) we will copy a special version file into the tar.gz and use > that instead. > > From an upstream point of view I think it is acceptable to say that the ones > that build stuff from a SCM (in contrast to a tarball) should have the files > of the SCM around...
well what if some used svn export <rev> to generate a tarball so it will break for him too. so distributors should package the SCM metadata and the user needs to have SCM tools to get the configure through. I would have added a script to update a constant var in src which would denote this incremental version like what gcc does with dates. > > PS: I liked the --exclude patch a lot too... > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > _______________________________________________ Bitbake-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bitbake-dev
