On Tue, 2 Dec 2025 at 03:12, Miaoqing Pan <[email protected]> wrote: > > I went and read the commit you reference: > > > > wpa-supplicant: Use upstream defconfig > > > > The copy of defconfig we were carrying was from 2014 and very out of > > date; drop it and use the upstream version with appropriate edits for > > our PACKAGECONFIG. > > > > So this was done for exactly the reasons I mentioned. Let's not go back > > there. > > Commit d97bedd8bdcc ("wpa-supplicant: Use upstream defconfig") uses the > defconfig from http://w1.fi/releases/wpa_supplicant-2.11.tar.gz rather > than from https://git.w1.fi/cgit/hostap/tree/wpa_supplicant/defconfig. > In other words, the copied defconfig without any modifications. By > maintaining own defconfig, ensure a consistent baseline and simplify the > process of enabling additional options.
It may be simpler for you to copy a file from upstream into oe-core and effectively make a fork, when you have modifications you'd like to make, but this creates a significant maintenance burden for the project that is already stretched very thin. How is the file going to be kept in sync with upstream? Who is going to do it, and what ensures they suddenly don't stop and disappear (this happens all the time)? How is the situation described in the commit message not going to repeat itself? Neither you, nor Dmitry are answering this, so please propose your needed changes to upstream, add them as backports, and devise a configuration/packageconfig mechanism in the recipe for things that need to be selected at build time. I know Debian does carry a copy, that in itself is not a reason to mimic them. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#227150): https://lists.openembedded.org/g/openembedded-core/message/227150 Mute This Topic: https://lists.openembedded.org/mt/116508467/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
