Moin, Am Sat, 10 Mar 2007 17:13:00 +0000 schrieb Richard Purdie:
> I disagree about the order. In my opinion, source version is part of > the package version. Hmm, ok. > You can control the order in PV, the examples I gave explicitly showed > how to do so. Ah, good point! Didn't notice that it would solve that part of the problem neatly. > There is one final variable that's been missing from these discussions > which is package epoch (PE). This is supported by the underlying tools > but not currently by bitbake itself. I mention it here as a change in > sever like this might be a case where PE would change. There are > patches around to add package epoch support around, waiting > integration. Ok, should the hypothetical situation arrive I can look into that, thanks. > I'm basically suggesting a build number based on when the sources last > changed is injected into PV, at least in the git case. In other SCM > cases, there are nicer numbers we can inject. I think I have a neat solution for git, profiting from the separation of (I)/(II) and (III): git rev-list gives a list of commit object names and simply counting the number of lines of the output should give a number similar to Last Changed Rev. However, this can only be used with an already downloaded local copy which is only available after fetching. Can the bitbake infrastructure support a different PV for the generated package? E.g. I would like to use the object name (sha-1) for determining when to recompile, before downloading and a `git rev-list | wc -l` equivalent for the generated packages, after downloading. > As I've said, I don't agree. I've made my argument for using PV, not > PR and there probably little else I can add. Ok, thank you very much for your input. Based on that I think I can create something that would be acceptable both to you for subsequent inclusion and to the openmoko people. -- Henryk Plötz Grüße aus Berlin ~ Help Microsoft fight software piracy: Give Linux to a friend today! ~ _______________________________________________ Bitbake-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bitbake-dev
