On 2008/03/31, Vlastimil Babka <[EMAIL PROTECTED]> wrote:
> I think that maybe we should first introduce new patching phase and
> then make this user patch really usable feature. For example if you
> want to patch something that's input to running autotools, doing it
> in post_src_unpack is too la
Peter Volkov <[EMAIL PROTECTED]> posted [EMAIL PROTECTED],
excerpted below, on Mon, 31 Mar 2008 14:15:45 +0400:
> It possible to use /etc/portage/bashrc to have this infrastructure.
> Search mailing list, it was discussed here at least twice, and this is
> example from solar:
>
> http://dev.gent
Mark Loeser wrote:
Mike Frysinger <[EMAIL PROTECTED]> said:
On Sunday 30 March 2008, Mark Loeser wrote:
Actually, I'd say this should just be removed. If a user wants to apply
a patch, they can put their own ebuild into an overlay and do it
themselves (presumably if they want to patch somethin
В Пнд, 31/03/2008 в 06:21 +, Duncan пишет:
> Mike Frysinger <[EMAIL PROTECTED]> posted
> [EMAIL PROTECTED], excerpted below, on Sun, 30 Mar
> 2008 20:39:14 -0400:
>
> > there is no package-manager specificness here. it's already completely
> > doable from a user perspective, just having it
Mike Frysinger <[EMAIL PROTECTED]> posted
[EMAIL PROTECTED], excerpted below, on Sun, 30 Mar
2008 20:39:14 -0400:
> there is no package-manager specificness here. it's already completely
> doable from a user perspective, just having it in the ebuild makes my
> life and users' lives easier. i'm
On Sunday 30 March 2008, Mark Loeser wrote:
> Mike Frysinger <[EMAIL PROTECTED]> said:
> > On Sunday 30 March 2008, Mark Loeser wrote:
> > > Actually, I'd say this should just be removed. If a user wants to
> > > apply a patch, they can put their own ebuild into an overlay and do it
> > > themselv
Ciaran McCreesh kirjoitti:
On Sun, 30 Mar 2008 17:18:44 -0400
Mark Loeser <[EMAIL PROTECTED]> wrote:
If it is something we want to move forward with, it should be
introduced at the package manager level instead of being an in-tree
package manager specific feature.
cat /etc/paludis/hooks/ebuild
On Sun, 30 Mar 2008 17:18:44 -0400
Mark Loeser <[EMAIL PROTECTED]> wrote:
> If it is something we want to move forward with, it should be
> introduced at the package manager level instead of being an in-tree
> package manager specific feature.
cat /etc/paludis/hooks/ebuild_unpack_post/patches.bash
Mark Loeser schrieb:
Mike Frysinger <[EMAIL PROTECTED]> said:
that's actually exactly what i'm encouraging. i'm not worried about such
issues as they're easily resolved by people posting the full build log.
Which is great, but I think this is something we should discuss and
figure out if this
Mike Frysinger <[EMAIL PROTECTED]> said:
> On Sunday 30 March 2008, Mark Loeser wrote:
> > Actually, I'd say this should just be removed. If a user wants to apply
> > a patch, they can put their own ebuild into an overlay and do it
> > themselves (presumably if they want to patch something, they'l
On Sunday 30 March 2008, Mark Loeser wrote:
> Donnie Berkholz <[EMAIL PROTECTED]> said:
> > On 17:26 Sat 29 Mar , Mike Frysinger (vapier) wrote:
> > > 1.1 sys-apps/iproute2/iproute2-2.6.24.20080108.ebuild
> > >
> > > file :
> > > http://sources.gentoo.org/viewcvs.py/gentoo-x86/
Donnie Berkholz <[EMAIL PROTECTED]> said:
> On 17:26 Sat 29 Mar , Mike Frysinger (vapier) wrote:
> > 1.1 sys-apps/iproute2/iproute2-2.6.24.20080108.ebuild
> >
> > file :
> > http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-apps/iproute2/iproute2-2.6.24.20080108.ebuild?rev=
On Sunday 30 March 2008, Donnie Berkholz wrote:
> On 17:26 Sat 29 Mar , Mike Frysinger (vapier) wrote:
> > 1.1 sys-apps/iproute2/iproute2-2.6.24.20080108.ebuild
> >
> > file :
> > http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-apps/iproute2/iproute
> >2-2.6.24.20080108.ebu
On 17:26 Sat 29 Mar , Mike Frysinger (vapier) wrote:
> 1.1 sys-apps/iproute2/iproute2-2.6.24.20080108.ebuild
>
> file :
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-apps/iproute2/iproute2-2.6.24.20080108.ebuild?rev=1.1&view=markup
> plain:
> http://sources.gentoo.or
14 matches
Mail list logo
