[RFC Wild Ideas Department] create soft-links from <pkg>/<src>/patches/some_local.patch to <oe.git>/packages/<pkg>/files/some_local.patch

[RFC Wild Ideas Department] create soft-links from <pkg>/<src>/patches/some_local.patch to <oe.git>/packages/<pkg>/files/some_local.patch

[Leon Woestenberg]

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.

Does this make sense?

Regards,
-- 
Leon

Re: [RFC Wild Ideas Department] create soft-links from <pkg>/<src>/patches/some_local.patch to <oe.git>/packages/<pkg>/files/some_local.patch

[Chris Larson]

On Wed, Dec 3, 2008 at 9:46 AM, Leon Woestenberg
<leon.woestenberg@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?
-- 
Chris Larson
clarson at kergoth dot com
clarson at mvista dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Software Engineer
MontaVista Software, Inc.

Re: [RFC Wild Ideas Department] create soft-links from <pkg>/<src>/patches/some_local.patch to <oe.git>/packages/<pkg>/files/some_local.patch

[Tom Rini]

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@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) ?

-- 
Tom Rini

Re: [RFC Wild Ideas Department] create soft-links from <pkg>/<src>/patches/some_local.patch to <oe.git>/packages/<pkg>/files/some_local.patch

[Khem Raj]

On Wed, Dec 3, 2008 at 9:51 AM, Tom Rini <trini@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@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@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: [RFC Wild Ideas Department] create soft-links from <pkg>/<src>/patches/some_local.patch to <oe.git>/packages/<pkg>/files/some_local.patch

[Leon Woestenberg]

Hello,

On Wed, Dec 3, 2008 at 6:51 PM, Tom Rini <trini@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@gmail.com> wrote:
>>
>> 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) ?
>
Exactly what I had in mind, for the reasons mentioned.

I only care about the local patches.

Edit source, quilt refresh, and my checkout has a modified patch.

Regards,
-- 
Leon

Re: [RFC Wild Ideas Department] create soft-links from <pkg>/<src>/patches/some_local.patch to <oe.git>/packages/<pkg>/files/some_local.patch

[Robert Schuster]

[-- Attachment #1: Type: text/plain, Size: 383 bytes --]

Hi,

Leon Woestenberg schrieb:
> Exactly what I had in mind, for the reasons mentioned.
> 
> I only care about the local patches.
> 
> Edit source, quilt refresh, and my checkout has a modified patch.
I like the idea, especially since I had to redo a few patch because I
forgot to copy them back to the checkout dir before doing "bitbake -c
rebuild".

Regards
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]

Re: [RFC Wild Ideas Department] create soft-links from <pkg>/<src>/patches/some_local.patch to <oe.git>/packages/<pkg>/files/some_local.patch

[Holger Freyther]

On Wednesday 03 December 2008 17:46:04 Leon Woestenberg 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.
>
> Does this make sense?

Yes it does, but I'm also toying with the idea of turning everything into a 
git checkout (using git am for the patches...)...

z.