OK, good to know. I mostly use gitk and it doesn't do a good job at following renames, so I thought that was the reason for this file structure.
Etienne On Wed, Jan 17, 2024 at 6:26 PM Ross Burton <ross.bur...@arm.com> wrote: > > On 17 Jan 2024, at 17:19, Etienne Cordonnier <ecordonn...@snap.com> wrote: > > > > Hi Ross, > > I thought the main reason of having .inc files was to have a stable git > > history, since the bb files get constantly renamed with each update? There > > are many recipes using a split .inc file without a need for it, so I > > assumed this is the standard codestyle of poky? Is it not the case? > > It originates from when openembedded had multiple versions for each recipe, > to share logic. > > Some people say that it helps track history, but unless you put _only_ the > checksums in the versioned file then you need to track the renamed file > anyway, and git’s “—follow” option does a reasonable job. I don’t consider > this a sufficient advantage considering the inconvenience of having a recipe > split arbitrarily between two files. > > Ross > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#193948): https://lists.openembedded.org/g/openembedded-core/message/193948 Mute This Topic: https://lists.openembedded.org/mt/103787498/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
