On Wednesday 10 March 2010 15:50:33 Tanstaafl wrote:
> Hello,
>
> I currently have 3 versions of automake installed (1.7.9-r1, 1.9.6-r3,
> and 1.10.2).
>
> emerge -pvuDN world shows an update available for each one, but, my
> question is, do I need all 3 versions?

Assuming you do not have those versions in world, the answer is:

yes

> 'equery depends automake' shows 44 packages, all depending on 1.10* or
> higher.

try running equery depends on a specific version or a SLOT.

equery lies through it's teeth. basically, it does a giant grep and tries to
format the output sensibly. Oftentimes, it doesn't succeed in the "sensibly"
department

> So, can I safely emerge -C the other 2 versions? Should I (does it even
> matter)?

No. The next emerge world will simply pull them back in. But they are build
depends so stuff won't stop working

You're first step though is to check for a dodgy world file with cruft in it.


--
alan dot mckinnon at gmail dot com

On Wed, 10 Mar 2010 08:50:33 -0500, Tanstaafl wrote:

> I currently have 3 versions of automake installed (1.7.9-r1, 1.9.6-r3,
> and 1.10.2).
>
> emerge -pvuDN world shows an update available for each one, but, my
> question is, do I need all 3 versions?
> 'equery depends automake' shows 44 packages,
> all depending on 1.10* or higher.
>
> So, can I safely emerge -C the other 2 versions? Should I (does it even
> matter)?

equery can be unreliable. If emerge --depclean -a wants to remove one of
both of them, let it, otherwise leave well alone.


--
Neil Bothwick

If Wile E. Coyote had enough money to buy all that ACME crap, why didn't
he just buy dinner?

On 03/10/2010 06:17 PM, walt wrote:

On 03/10/2010 05:50 AM, Tanstaafl wrote:

Hello,

I currently have 3 versions of automake installed (1.7.9-r1, 1.9.6-r3,
and 1.10.2).

emerge -pvuDN world shows an update available for each one, but, my
question is, do I need all 3 versions?

'equery depends automake' shows 44 packages, all depending on 1.10* or
higher.

So, can I safely emerge -C the other 2 versions? Should I (does it even
matter)?


Probably won't matter. A few packages actually specify an exact version
of the autotools, but most just want a certain minimum version.


Portage doesn't allow ebuilds to specify minimum versions or ranges for
automake, only exact versions.


Specifying a mininum only works when putting automake as a dep in
DEPEND. However, Gentoo devs are required to use WANT_AUTOMAKE, not
DEPEND and WANT_AUTOMAKE only allows specific versions, not minimum ones.


And this means multiple automake versions on the system are perfectly
normal.

On 2010-03-10 1:45 PM, Nikos Chantziaras wrote:
> And this means multiple automake versions on the system are perfectly
> normal.

Ok, that's what I needed to hear...

Thanks Nikos...

--

Charles

On 2010-03-10 12:05 PM, Neil Bothwick wrote:
> equery can be unreliable. If emerge --depclean -a wants to remove one
> of both of them, let it, otherwise leave well alone.

Understood, thanks...

Just to be sure... the -a in the 'emerge --depclean -a' above will 'ask'
me if I want to continue and remove the packages it finds, correct?
Meaning, it won't just blindly go ahead and start ripping stuff out...

How does that differ from 'emerge -p --depclean'?

--

Charles

On 03/10/2010 10:16 PM, Tanstaafl wrote:

On 2010-03-10 12:05 PM, Neil Bothwick wrote:

equery can be unreliable. If emerge --depclean -a wants to remove one
of both of them, let it, otherwise leave well alone.


Understood, thanks...

Just to be sure... the -a in the 'emerge --depclean -a' above will 'ask'
me if I want to continue and remove the packages it finds, correct?
Meaning, it won't just blindly go ahead and start ripping stuff out...

How does that differ from 'emerge -p --depclean'?


"emerge -p" will only print what it would merge/unmerge and then quits
without asking. You can run this as normal user, no need to be root.


"emerge -a" will print what it would merge/unmerge and then ask if you
want to proceed. You have to be root to use this command.


If you are not root and use "emerge -a", portage will turn it into an
"emerge -p" and tell you that it did so because you are not root.

On Wed, Mar 10, 2010 at 2:16 PM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
> On 2010-03-10 12:05 PM, Neil Bothwick wrote:
>> equery can be unreliable. If emerge --depclean -a wants to remove one
>> of both of them, let it, otherwise leave well alone.
>
> Understood, thanks...
>
> Just to be sure... the -a in the 'emerge --depclean -a' above will 'ask'
> me if I want to continue and remove the packages it finds, correct?
> Meaning, it won't just blindly go ahead and start ripping stuff out...
>
> How does that differ from 'emerge -p --depclean'?

Saves you the time of running it twice if you decide to say "Yes"

On Wed, 10 Mar 2010 15:16:14 -0500, Tanstaafl wrote:

> Just to be sure... the -a in the 'emerge --depclean -a' above will 'ask'
> me if I want to continue and remove the packages it finds, correct?
> Meaning, it won't just blindly go ahead and start ripping stuff out...

Yes.

> How does that differ from 'emerge -p --depclean'?

With -p you have to run the command again, and let is scan all installed
packages and their deps again, when you want it to actually remove them.
It's just a more efficient way of doing it.


--
Neil Bothwick

"I am Homer of the Borg. You will be assim.... Hmm... Donuts..."

On 03/10/2010 10:45 AM, Nikos Chantziaras wrote:

On 03/10/2010 06:17 PM, walt wrote:



A few packages actually specify an exact version
of the autotools, but most just want a certain minimum version.


Portage doesn't allow ebuilds to specify minimum versions or ranges for automake, only exact versions.


Oops, I was actually thinking of how the autotools can specify minimum
versions of required libraries. Libraries != autotools

On 2010-03-10 4:05 PM, Paul Hartman wrote:
> On Wed, Mar 10, 2010 at 2:16 PM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
>> On 2010-03-10 12:05 PM, Neil Bothwick wrote:
>>> equery can be unreliable. If emerge --depclean -a wants to remove one
>>> of both of them, let it, otherwise leave well alone.

>> How does that differ from 'emerge -p --depclean'?

> Saves you the time of running it twice if you decide to say "Yes"

Well that was kind of obvious... ok, thanks...

--

Charles