On Sun, 24 Apr 2011 21:17:23 +0100, David W Noon wrote:

> >Doing this today I've had a couple of packages that needed to be
> >emerged with USE=-doc when they failed.
>
> Those would be jinja and sphinx. They are notorious for their circular
> dependency, which requires USE='-doc' to bypass.

It's rarely desirable to enable doc globally. It is best to enable only
for those packages where you need extended documentation.


--
Neil Bothwick

A bit of tolerance is worth a megabyte of flaming. -- Henry Spencer

On Sunday 24 April 2011 21:30:33 Neil Bothwick wrote:
> On Sun, 24 Apr 2011 21:17:23 +0100, David W Noon wrote:
> > >Doing this today I've had a couple of packages that needed to be
> > >emerged with USE=-doc when they failed.
> >
> > Those would be jinja and sphinx. They are notorious for their circular
> > dependency, which requires USE='-doc' to bypass.
>
> It's rarely desirable to enable doc globally. It is best to enable only
> for those packages where you need extended documentation.

@Alan Mackenzie:

What Neil is saying can be achieved by setting package specific USE flags in
the file /etc/portage/package.use; e.g. use an entry like:

dev-python/jinja -doc i18n

to exclude USE flag "doc", but include "i18n".
--
Regards,
Mick

On Sun, 24 Apr 2011 23:16:39 +0100, Mick wrote:

> > It's rarely desirable to enable doc globally. It is best to enable
> > only for those packages where you need extended documentation.
>
> @Alan Mackenzie:
>
> What Neil is saying can be achieved by setting package specific USE
> flags in the file /etc/portage/package.use; e.g. use an entry like:

What I'm saying is that you should have -doc in /etc/make.conf and enable
it on a per-package basis. The doc flag builds extra documentation that
general users don't need, man/info/html pages are included by default (at
least, that's how it is supposed to work, the odd package, like ffmpeg,
won't even include a man page without the doc flag).


--
Neil Bothwick

This is as bad as it can get-but don't bet on it.

On Monday 25 April 2011 08:30:58 Neil Bothwick wrote:
> On Sun, 24 Apr 2011 23:16:39 +0100, Mick wrote:
> > > It's rarely desirable to enable doc globally. It is best to enable
> > > only for those packages where you need extended documentation.
> >
> > @Alan Mackenzie:
> >
> > What Neil is saying can be achieved by setting package specific USE
>
> > flags in the file /etc/portage/package.use; e.g. use an entry like:
> What I'm saying is that you should have -doc in /etc/make.conf and enable
> it on a per-package basis. The doc flag builds extra documentation that
> general users don't need, man/info/html pages are included by default (at
> least, that's how it is supposed to work, the odd package, like ffmpeg,
> won't even include a man page without the doc flag).

The doc USE flag is disabled by default on my make.profile
(amd64/10.0/desktop), so although it won't need to be set as -doc in
/etc/make.conf, it will need to be set as doc in the packages that need it in
/etc/portage/package.use.
--
Regards,
Mick

On Mon, 25 Apr 2011 08:49:35 +0100, Mick wrote:

> > What I'm saying is that you should have -doc in /etc/make.conf and
> > enable it on a per-package basis. The doc flag builds extra
> > documentation that general users don't need, man/info/html pages are
> > included by default (at least, that's how it is supposed to work, the
> > odd package, like ffmpeg, won't even include a man page without the
> > doc flag).
>
> The doc USE flag is disabled by default on my make.profile
> (amd64/10.0/desktop), so although it won't need to be set as -doc in
> /etc/make.conf, it will need to be set as doc in the packages that need
> it in /etc/portage/package.use.

I know it's disabled by default, but it seems like the OP has enabled it
globally.


--
Neil Bothwick

"When you play a Microsoft CD backwards you can hear demonic Voices...
that's nothing - when you play it forward it installs Windows"

Hi, Neil.

A happy Easter to everybody who celebrates it, and a very good day to
everybody else!

On Mon, Apr 25, 2011 at 11:07:15AM +0100, Neil Bothwick wrote:
> On Mon, 25 Apr 2011 08:49:35 +0100, Mick wrote:

> > The doc USE flag is disabled by default on my make.profile
> > (amd64/10.0/desktop), so although it won't need to be set as -doc in
> > /etc/make.conf, it will need to be set as doc in the packages that
> > need it in /etc/portage/package.use.

> I know it's disabled by default, but it seems like the OP has enabled it
> globally.

Not me! The handbook strongly recommended against doing this.

> --
> Neil Bothwick

--
Alan Mackenzie (Nuremberg, Germany).

Hi, Mick.

On Sun, Apr 24, 2011 at 04:44:05PM +0100, Mick wrote:
> On Sunday 24 April 2011 14:25:58 Alan Mackenzie wrote:
> > Hi, Mick.

> > On Sun, Apr 24, 2011 at 09:17:45AM +0100, Mick wrote:
> > > On Saturday 23 April 2011 21:06:25 Alan Mackenzie wrote:
> > > > On Sat, Apr 23, 2011 at 08:46:30PM +0100, Mick wrote:

> > > python-updater -v -p

> > > to get a list of these.

> > That gives me a list of 24 packages. Am I meant to actually run
> > python-updater without the -p, here?

> That's correct. As the man emerge say -p stands for --pretend. Just
> to give a chance to see what it wants to do and think about it before
> you run it again without it for execution.

> You need to do this next.

DONE.

> > > When you finish all this you can run:

> > > emerge --depclean -v -p

> > > It should now ask you to remove the old python, but check carefully
> > > the remaining packages in case something important is in the list
> > > and breaks your system.

> > I do emerge --depclean -v -p. It says I should run emerge -uDN
> > @world first. I'm a bit apprehensive about this, since the world
> > update says it would reemerge 138 packages (I'm not sure whether this
> > is top-level (whatever that means) packages or the real total). In
> > that list are 3 blockages I don't know wha do do with. My experience
> > suggests this will not work smoothly, and I'll likely be left with a
> > non-working (or even a non-bootable) system.

> At this stage you should only run:

> python-updater -v

> Nothing else.

> Once it completes you can run --depclean which will ask you to remove
> the older 2.6 python package.

I had to (or, at least, did) run emerge -uND @world. Funnily enough, it
ran to completion without manual intervention. :-) I'd like to run
--depclean, but it's threatening to remove my 2.6.31-r6 kernel sources,
which correspond to my working kernel. What's the easiest way to protect
these from --depclean?

> --
> Regards,
> Mick

--
Alan Mackenzie (Nuremberg, Germany).

On 25/4/2011, at 11:07am, Neil Bothwick wrote:
>> ...
>> The doc USE flag is disabled by default on my make.profile
>> (amd64/10.0/desktop), so although it won't need to be set as -doc in
>> /etc/make.conf, it will need to be set as doc in the packages that need
>> it in /etc/portage/package.use.
>
> I know it's disabled by default, but it seems like the OP has enabled it
> globally.

In case you're mistaking me for the OP: I have it enabled globally, I just mentioned the necessity of disabling it for some packages in case the OP came across the same problem.

Maybe I should disable doc, but it seems "wrong" to me, to miss out on all this potentially useful information (which admittedly I never use).

Stroller.

On Mon, 25 Apr 2011 13:18:22 +0100, Stroller wrote:

> Maybe I should disable doc, but it seems "wrong" to me, to miss out on
> all this potentially useful information (which admittedly I never use).

The potentially useful information is installed anyway. USE=doc enables
the potentially useless information ;-)


--
Neil Bothwick

Happiness is merely the remission of pain.

On Monday 25 April 2011 13:11:53 Alan Mackenzie wrote:
> Hi, Mick.
>
> On Sun, Apr 24, 2011 at 04:44:05PM +0100, Mick wrote:
> > On Sunday 24 April 2011 14:25:58 Alan Mackenzie wrote:
> > > Hi, Mick.
> > >
> > > On Sun, Apr 24, 2011 at 09:17:45AM +0100, Mick wrote:
> > > > On Saturday 23 April 2011 21:06:25 Alan Mackenzie wrote:
> > > > > On Sat, Apr 23, 2011 at 08:46:30PM +0100, Mick wrote:
> > > > python-updater -v -p
> > > >
> > > > to get a list of these.
> > >
> > > That gives me a list of 24 packages. Am I meant to actually run
> > > python-updater without the -p, here?
> >
> > That's correct. As the man emerge say -p stands for --pretend. Just
> > to give a chance to see what it wants to do and think about it before
> > you run it again without it for execution.
> >
> > You need to do this next.
>
> DONE.
>
> > > > When you finish all this you can run:
> > > >
> > > > emerge --depclean -v -p
> > > >
> > > > It should now ask you to remove the old python, but check carefully
> > > > the remaining packages in case something important is in the list
> > > > and breaks your system.
> > >
> > > I do emerge --depclean -v -p. It says I should run emerge -uDN
> > > @world first. I'm a bit apprehensive about this, since the world
> > > update says it would reemerge 138 packages (I'm not sure whether this
> > > is top-level (whatever that means) packages or the real total). In
> > > that list are 3 blockages I don't know wha do do with. My experience
> > > suggests this will not work smoothly, and I'll likely be left with a
> > > non-working (or even a non-bootable) system.
> >
> > At this stage you should only run:
> >
> > python-updater -v
> >
> > Nothing else.
> >
> > Once it completes you can run --depclean which will ask you to remove
> > the older 2.6 python package.
>
> I had to (or, at least, did) run emerge -uND @world. Funnily enough, it
> ran to completion without manual intervention. :-) I'd like to run
> --depclean, but it's threatening to remove my 2.6.31-r6 kernel sources,
> which correspond to my working kernel. What's the easiest way to protect
> these from --depclean?

Aha! That's why I said first look at what it wants to remove - you don't want
to cripple your system. In this case of course it won't cripple anything,
because it won't remove the kernel image from /boot/

If you look in /usr/src/linux/ you will see a number of kernel sources listed
in there. If you've run update world there should be a more up-to-date kernel
awaiting for you to configure and compile it. Do that first; copy the
necessary files into /boot; configure grub.conf to boot with you latest
kernel; and after you boot into it and check that all is good you can allow --
depclean to remove older kernel source files.

PS. You may need to manually remove older source files left in
/usr/src/linux/ when depclean completes its job.
--
Regards,
Mick