> On Tue, 3 May 2016, Austin English wrote:
> I've been working on the transition from #!/sbin/runscript to
> #!/sbin/openrc-run [1], by starting on the maintainer-needed
> packages. That's done (aside from some stabilizations needed, but
> I'll deal with that latter). The trouble is that ther
On 05/04/2016 02:04 AM, Ulrich Mueller wrote:
>> On Tue, 3 May 2016, Austin English wrote:
>> I've been working on the transition from #!/sbin/runscript to
>> #!/sbin/openrc-run [1], by starting on the maintainer-needed
>> packages. That's done (aside from some stabilizations needed, but
>> I'l
> On Wed, 4 May 2016, Austin English wrote:
>> Your list of affected packages obtained with "git grep" in the
>> Portage tree will not be complete, since the command won't catch
>> any init scripts installed from elsewhere. You should look for the
>> set of installed files instead.
> How is t
On 05/04/2016 06:46 AM, Matt Turner wrote:
> On Tue, May 3, 2016 at 5:50 PM, Mike Gilbert wrote:
>> On Tue, May 3, 2016 at 5:34 PM, Jeroen Roovers wrote:
>>> The solution is to have people with an actual interest in a specific
>>> architecture determine whether stabilising a package is viable, an
On Wed, May 04, 2016 at 10:00:05AM +0200, Ulrich Mueller wrote:
> > On Wed, 4 May 2016, Austin English wrote:
>
> >> Your list of affected packages obtained with "git grep" in the
> >> Portage tree will not be complete, since the command won't catch
> >> any init scripts installed from elsewhe
On 05/04/2016 10:52 AM, Sam Jorna wrote:
> On Wed, May 04, 2016 at 10:00:05AM +0200, Ulrich Mueller wrote:
>>> On Wed, 4 May 2016, Austin English wrote:
>>
Your list of affected packages obtained with "git grep" in the
Portage tree will not be complete, since the command won't catch
>
Ulrich Mueller posted on Wed, 04 May 2016 10:00:05 +0200 as excerpted:
>> On Wed, 4 May 2016, Austin English wrote:
>
>>> Your list of affected packages obtained with "git grep" in the Portage
>>> tree will not be complete, since the command won't catch any init
>>> scripts installed from els
On Wed, May 04, 2016 at 10:57:44AM +0200, Kristian Fiskerstrand wrote:
> On 05/04/2016 10:52 AM, Sam Jorna wrote:
> > On Wed, May 04, 2016 at 10:00:05AM +0200, Ulrich Mueller wrote:
> >>> On Wed, 4 May 2016, Austin English wrote:
> >>
> Your list of affected packages obtained with "git gre
On Wed, May 4, 2016 at 12:46 AM, Matt Turner wrote:
> Having built many stages for an "unstable" arch (mips) has taught me
> one thing: it's awful being unstable-only. There's no end to the
> compilation failures and other such headaches, none of which have
> anything at all to do with the specifi
On 04.05.2016 11:19, Duncan wrote:
> Ulrich Mueller posted on Wed, 04 May 2016 10:00:05 +0200 as excerpted:
>
>>> On Wed, 4 May 2016, Austin English wrote:
>>
Your list of affected packages obtained with "git grep" in the Portage
tree will not be complete, since the command won't cat
On 04.05.2016 14:54, Manuel Rüger wrote:
> On 04.05.2016 11:19, Duncan wrote:
>> Ulrich Mueller posted on Wed, 04 May 2016 10:00:05 +0200 as excerpted:
>>
On Wed, 4 May 2016, Austin English wrote:
>>>
> Your list of affected packages obtained with "git grep" in the Portage
> tree w
Mike Gilbert wrote:
> "doing your job"
Remember that everyone is a volunteer.
> dropping stable keywords on everything but the bare necessities
Gentoo magically does a number of things which upstream never
intended and do not intentionally support. It is amazing, and
thank you so much to everyo
prends soin de toi
On Tue, May 3, 2016 at 11:43 AM Sven Vermeulen wrote:
> On Sun, May 01, 2016 at 04:57:09PM +0200, José Fournier wrote:
> > I have been a bit far from Gentoo for a rather long time now. I joined
> > Gentoo in 2013 and I used to be a translator for the French language. At
> > th
On 04/05/16 02:01 AM, Kent Fredric wrote:
> On 4 May 2016 at 16:46, Matt Turner wrote:
>> Having built many stages for an "unstable" arch (mips) has taught me
>> one thing: it's awful being unstable-only. There's no end to the
>> compilation failures and other such headaches, none of which have
>>
On Wed, May 4, 2016 at 10:41 AM, Peter Stuge wrote:
> Mike Gilbert wrote:
>> "doing your job"
>
> Remember that everyone is a volunteer.
I am referring to arch testing as a job, because it only really works
if people treat it that way. If stabilization does not take place in a
timely manner, the
On 05/04/2016 11:41 AM, Ian Stakenvicius wrote:
On 04/05/16 02:01 AM, Kent Fredric wrote:
On 4 May 2016 at 16:46, Matt Turner wrote:
Having built many stages for an "unstable" arch (mips) has taught me
one thing: it's awful being unstable-only. There's no end to the
compilation failures and
On Wed, May 4, 2016 at 8:44 AM, Mike Gilbert wrote:
> On Wed, May 4, 2016 at 10:41 AM, Peter Stuge wrote:
>> Mike Gilbert wrote:
>>> "doing your job"
>>
>> Remember that everyone is a volunteer.
>
> I am referring to arch testing as a job, because it only really works
> if people treat it that wa
hum... yes I've setup all the relevant settings in my /etc/portage...
I've also read the man, and still not understanding why.
But At least you are confirming me that directly modifying the user.eclass in
/usr/portage/eclass should work!
The exact command line I've used was ROOT=/sysroot emerge
On 04/05/16 02:30 PM, Farid BENAMROUCHE wrote:
> hum... yes I've setup all the relevant settings in my /etc/portage...
> I've also read the man, and still not understanding why.
>
> But At least you are confirming me that directly modifying the user.eclass in
> /usr/portage/eclass should work!
>
On Tue, May 03, 2016 at 09:46:10PM -0700, Matt Turner wrote
> On Tue, May 3, 2016 at 5:50 PM, Mike Gilbert wrote:
> > On Tue, May 3, 2016 at 5:34 PM, Jeroen Roovers wrote:
> >> The solution is to have people with an actual interest in a specific
> >> architecture determine whether stabilising a p
On 04/05/16 03:43 PM, waltd...@waltdnes.org wrote:
>
> emerge --keyword-write
>
> ... similar to "emerge --autounmask-write", but have it write to
> package.accept_keywords, rather than package.unmask?
>
> That would achieve the effect that people are looking for, with less
> work.
>
--auto
On Wed, May 04, 2016 at 04:05:50PM -0400, Ian Stakenvicius wrote
> On 04/05/16 03:43 PM, waltd...@waltdnes.org wrote:
> >
> > emerge --keyword-write
> >
> > ... similar to "emerge --autounmask-write", but have it write to
> > package.accept_keywords, rather than package.unmask?
> >
> > That wo
ok, thank you.I will try the chroot stuff as soon as I have some time.
As for what I'm trying to do: making portage able to add user/groups when using
--root option.
This is a known limitation since a long time. I'm currently also discussing
this point with the "shadow" upstream team (I have som
On Wed, May 04, 2016 at 07:41:39PM +1000, Sam Jorna wrote:
> On Wed, May 04, 2016 at 10:57:44AM +0200, Kristian Fiskerstrand wrote:
> > On 05/04/2016 10:52 AM, Sam Jorna wrote:
> > > On Wed, May 04, 2016 at 10:00:05AM +0200, Ulrich Mueller wrote:
> > >>> On Wed, 4 May 2016, Austin English wrote
On 05/05/2016 01:12 AM, William Hubbs wrote:
> On Wed, May 04, 2016 at 07:41:39PM +1000, Sam Jorna wrote:
>> On Wed, May 04, 2016 at 10:57:44AM +0200, Kristian Fiskerstrand wrote:
>>> On 05/04/2016 10:52 AM, Sam Jorna wrote:
On Wed, May 04, 2016 at 10:00:05AM +0200, Ulrich Mueller wrote:
>
25 matches
Mail list logo
