Obviously that class (devupstream.bbclass) is not in the YP reference manual. I will open a bug to document it.
Scott On Fri, May 4, 2018 at 6:12 AM, Paulo Neves <ptsne...@gmail.com> wrote: > On Fri, May 4, 2018 at 2:55 PM, Burton, Ross <ross.bur...@intel.com> > wrote: > > On 4 May 2018 at 13:46, Paulo Neves <ptsne...@gmail.com> wrote: > >> > >> I always wondered, what is the rationale for not always using the git > >> repositories? If there is one why did we change for this specific > >> recipe? > > > > > > Tarballs are easier to mirror, smaller, have checksums to verify the > > download at both fetch and unpack time, and often contain generated files > > which otherwise require yet more tools to regenerate (for example, man > pages > > may require a documentation toolchain to build from git but will be > included > > in a tarball). > In my case we have a requirement of using the git repositories because > of the easiness with which we can make code bissections, as well as > back porting. > > >> > >> I ask this because I am in the process of creating a massive layer, > >> whose only purpose is to have the software come from the git > >> repository and not from the tarballs of the original poky recipes. > > > > > > I certainly hope this is using devupstream.bbclass or similar and isn't a > > giant copy/paste! > Wow never heard/saw of this bbclass even, and looking at the mega > manual there is not any reference to this class. Also from the look of > the classcode I am not seeing how this can help us accomplish the > goal. Can you point me to some docs or examples? > > > Ross > > The way we are doing the layer is, by bbappend, so there is not much > copy paste, but tarbal/git replacement. > There would be no problem if there would not be differences between > released tarballs and git repositories, but specially in autotools > projects, the bbappend requires much more trickery as you mentioned > > Paulo Neves > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core >
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
