[oe] [RFC Wild Ideas Department] create soft-links from <pkg>/<src>/patches/some_local.patch to <oe.git>/packages/<pkg>/files/some_local.patch
raj.khem at gmail.com
Wed Dec 3 20:49:08 CET 2008
On Wed, Dec 3, 2008 at 9:51 AM, Tom Rini <trini at kernel.crashing.org> wrote:
> On Wed, Dec 03, 2008 at 10:00:13AM -0700, Chris Larson wrote:
>> On Wed, Dec 3, 2008 at 9:46 AM, Leon Woestenberg
>> <leon.woestenberg at gmail.com> wrote:
>> > Hello,
>> > during maintenance of our local set of OE patches, it would be handy
>> > not having to copy patches back into the repository.
>> > i.e. the patch fetcher could instead of copy the patch to the work
>> > directory, soft-link from the repo.
>> I can see why you want it. The file:// fetcher copies everything,
>> not just patches, they aren't fetched differently currently. You
>> could introduce regressions if it were to affect anything but patches,
>> so you'd have to add a special case for uris with patch=1 in the
>> file:// fetcher to link instead of copy, and possibly make it optional
>> via a variable. I take it you do a lot of patch alterations in the
>> workdir to fix problems?
> A lot? No. But for everyone working from a fixed OE snapshot, this
> would be a nice timesaver. Heck, soft-linking all of the file URIs
> would be nice here. Perhaps a variable to control doing it always
> (default to off) ?
We use quilt to manage (push/pop) patches. We could use
QUILT_PATCHES=<dir where patches are found> in .quiltrc file.One
problem I see is that sometimes we use patches from more than one
location. Sometimes we develop patches on top and how do we decide
where this patch is put if we have more
than one locations for the patches.
> Tom Rini
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
More information about the Openembedded-devel