AdminChris Larson
(Admin, OpenEmbedded)
-
1 voteAdminChris Larson
(Admin, OpenEmbedded)
shared this idea and gave it 1 vote
·
-
1 votecompleted ·AdminChris Larson
(Admin, OpenEmbedded)
responded
srctree.bbclass & gitver.bbclass have gotten us most of the way there on this. If more work remains to be done, it’ll be as bugfixes via the bugzilla, most likely.
AdminChris Larson
(Admin, OpenEmbedded)
gave this 1 vote
·
AdminChris Larson
(Admin, OpenEmbedded)
shared this idea
·
-
5 votesAdminChris Larson
(Admin, OpenEmbedded)
shared this idea and gave it 3 votes
·
-
12 votesAdminChris Larson
(Admin, OpenEmbedded)
gave this 1 vote
·
-
2 votesAdminChris Larson
(Admin, OpenEmbedded)
gave this 1 vote
·
-
3 votesAdminChris Larson
(Admin, OpenEmbedded)
gave this 2 votes
·
-
8 votesAdminChris Larson
(Admin, OpenEmbedded)
responded
This is a great idea, in my opinion. I’m certain I’m not the only one to run a ls —sort=time —reverse | head -n 1 to grab the latest log, or to do a -c clean and rebuild of the thing just to clean out the temp dir :)
AdminChris Larson
(Admin, OpenEmbedded)
gave this 1 vote
·
Narcissus is a great tool, but it hides the build process. What I'm talking about would be a native interface, and more flexible, and wouldn't abstract away the build process. The image recipes would go away, in favor of template configurations passed to the image builder. Narcissus shouldn't go away, there's a definite need for it, but it can live alongside a tool like I propose here.