On 2012-04-18 01:07, Paul Eggleton wrote:
On Wednesday 18 April 2012 00:35:29 Ulf Samuelsson wrote:
Today bitbake supports read only git access in recipes.
For various reasons, I would like to be able to do recipes
which would check out in a read/write mode.
Could you elaborate on "various reasons"?
Would the new externalsrc bbclass be useful in your case?
Cheers,
Paul
1. If I am busy working on an application, then it simplifies the
development process.
I can modify the code in the tree and push.
This is mainly for kernel development.
2. If I work on a prerelease of some S/W drivers/Applications under NDA,
then I cannot make that code publicly available
but I still want to put that on my Internet accessible git server.
Typicailly this is before the release of a new chip and info about
the chip should not be
made public before the chip is released.
3. I want to be able to ship something similar to the Angstrom setup
scripts
to someone else, and have them build an image, but it should not
be available
to anyone not accepted (without public key at the git server).
There are other uses for such a functionality, but those are my
immediate needs.
As you see, this is mostly for development.
Once the code is released, then the recipe would be changed to the
normal git access.
Didn't know anything about the externalsrc bbclass, but after checking,
I would say no.
It won't do the two things above. I do see the use of it though.
--
Best Regards
Ulf Samuelsson
u...@emagii.com
+46 722 427437
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
