Historically, when an update to portage came available, portage would
put it at the head of the list, build it first, then re-run emerge
world command.

I've seen lately that this no longer happens, portage updates are any
old place in the list just like all other packages.

I'm wondering why this change happened, or if I somehow unknowingly set
an option to disable the old behaviour )I'd liek it back).


--
Alan McKinnnon
alan.mckinnon@gmail.com

On Thu, 23 Feb 2012 13:16:01 +0200, Alan McKinnon wrote:

> Historically, when an update to portage came available, portage would
> put it at the head of the list, build it first, then re-run emerge
> world command.
>
> I've seen lately that this no longer happens, portage updates are any
> old place in the list just like all other packages.
>
> I'm wondering why this change happened, or if I somehow unknowingly set
> an option to disable the old behaviour )I'd liek it back).

It's not just you, although it doesn't appear to be that random.
Generally the portage update comes at or near the end of the list here.

At least you get the rest of the world update done before a broken new
portage renders it unusable :-/


--
Neil Bothwick

Normal people believe that if it ain't broke, don't fix it. Engineers
believe that if it ain't broke, it doesn't have enough features yet."

On Thu, 23 Feb 2012 11:24:17 +0000
Neil Bothwick <neil@digimed.co.uk> wrote:

> On Thu, 23 Feb 2012 13:16:01 +0200, Alan McKinnon wrote:
>
> > Historically, when an update to portage came available, portage
> > would put it at the head of the list, build it first, then re-run
> > emerge world command.
> >
> > I've seen lately that this no longer happens, portage updates are
> > any old place in the list just like all other packages.
> >
> > I'm wondering why this change happened, or if I somehow unknowingly
> > set an option to disable the old behaviour )I'd liek it back).
>
> It's not just you, although it doesn't appear to be that random.
> Generally the portage update comes at or near the end of the list
> here.
>
> At least you get the rest of the world update done before a broken new
> portage renders it unusable :-/

:-)

I prefer to update portage first, just in case it co-coincides with some
update to the tree <pedantic old fart mode ON>

I'm not worried about broken portage commits, I have
FEATURES="buildsyspkg" enabled so as long as I have a working tar I'm
good to go with any fix.


--
Alan McKinnnon
alan.mckinnon@gmail.com

On Thu, Feb 23, 2012 at 01:48:59PM +0200, Penguin Lover Alan McKinnon squawked:
> I'm not worried about broken portage commits, I have
> FEATURES="buildsyspkg" enabled so as long as I have a working tar I'm
> good to go with any fix.

Wait... isn't portage itself no longer in the system set?

W
--
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire
et vice versa ~~~ I. Newton

On Thu, 23 Feb 2012 15:07:46 +0100
Willie WY Wong <wongwwy@member.ams.org> wrote:

> On Thu, Feb 23, 2012 at 01:48:59PM +0200, Penguin Lover Alan McKinnon
> squawked:
> > I'm not worried about broken portage commits, I have
> > FEATURES="buildsyspkg" enabled so as long as I have a working tar
> > I'm good to go with any fix.
>
> Wait... isn't portage itself no longer in the system set?
>
> W

I believe you are right, portage is now just a package manager that
satisfies virtual/package-manager

--
Alan McKinnnon
alan.mckinnon@gmail.com

On Thursday 23 February 2012 11:48:59 Alan McKinnon wrote:

*

> I prefer to update portage first, just in case it co-coincides with some

> update to the tree <pedantic old fart mode ON>

*

What does "co-coincides" mean? I know that various versions of English exist out there, but this one has me foxed.

*

--

Rgds

Peter Linux Counter 5290, 1994-04-23

*

On Fri, 24 Feb 2012 01:36:00 +0000
Peter Humphrey <peter@humphrey.ukfsn.org> wrote:

> On Thursday 23 February 2012 11:48:59 Alan McKinnon wrote:
>
> > I prefer to update portage first, just in case it co-coincides with
> > some update to the tree <pedantic old fart mode ON>
>
> What does "co-coincides" mean? I know that various versions of
> English exist out there, but this one has me foxed.
>

That would be because it's a mistake :-)

coincides

--
Alan McKinnnon
alan.mckinnon@gmail.com

On Fri, Feb 24, 2012 at 01:36:00AM +0000, Penguin Lover Peter Humphrey squawked:
> On Thursday 23 February 2012 11:48:59 Alan McKinnon wrote:
>
> > I prefer to update portage first, just in case it co-coincides with some
> > update to the tree <pedantic old fart mode ON>
>
> What does "co-coincides" mean? I know that various versions of English exist
> out there, but this one has me foxed.

When Alan puts on his pedantic old fart hat, sometimes he gets so
excited that he stutters a little bit.



W
--
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire
et vice versa ~~~ I. Newton

On Fri, 24 Feb 2012 01:36:00 +0000, Peter Humphrey wrote:

> > I prefer to update portage first, just in case it co-coincides with
> > some update to the tree <pedantic old fart mode ON>
>
> What does "co-coincides" mean?

It's when two coincidences are mutually coincident.

That or something involving a hot bedtime drink


--
Neil Bothwick

The law of Probability Dispersal decrees that whatever it is that hits
the fan will not be evenly distributed.

On Feb 24, 2012 4:08 PM, "Neil Bothwick" <neil@digimed.co.uk> wrote:

>

> On Fri, 24 Feb 2012 01:36:00 +0000, Peter Humphrey wrote:

>

> > > I prefer to update portage first, just in case it co-coincides with

> > > some update to the tree <pedantic old fart mode ON>

> >

> > What does "co-coincides" mean?

>

> It's when two coincidences are mutually coincident.

>

> That or something involving a hot bedtime drink

>


More likely one nightcap too many ;-)


(Gosh, I love this list because all the friendly meta ribbings)


Rgds,