On Tue, 2024-11-12 at 18:46 +0000, Mark Asselstine via lists.openembedded.org wrote: > On 11/12/2024 1:13 PM, Mark Hatle wrote: > > On 11/12/24 12:05 PM, Mark Asselstine via lists.openembedded.org > > wrote: > >
> > include_all conf/maintainers.inc > > > > vs > > > > include conf/maintainers* > > > > The first one though would go through ALL of the search paths and > > include all of the files with a specific path/name. > > > > If the second even works, I would expect it to include the first > > maintainers file it found, not all of them.. but even if it did > > more > > then once, it would be from the first search path and stop. > > Again, using the globbing as you would for ls or rm there would be no > expectation to stop at the first one. It would follow an established > pattern found elsewhere in Linux commands. I think the concern is that this is at least a little ambiguous. People expect "include" to process one file. Does "include conf/maintainers*" stop at the first matching file found in BBPATH or not? Also, what I feel we're looking for is something like: include_all conf/distro/includes/maintainers.inc which with globbing would equate to: include_all */conf/distro/includes/maintainers.inc which then gets very confused about the layer prefix which usually isn't included in these paths. For those reasons I'm a lot happier with the explcit nature of include_all. I appreciate the other case could be more inventive and flexible but that isn't really a good thing IMO, it feels like we have a bit too much of that currently. Cheers, Richard >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2076): https://lists.openembedded.org/g/openembedded-architecture/message/2076 Mute This Topic: https://lists.openembedded.org/mt/109425270/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
