Re: [gentoo-user] Re: [OT] How to be a penguin.

[Gregory Woodbury]

On Sun, May 29, 2016 at 8:13 AM, Alan Grimes <ALONZOTG@×××××××.net> wrote:

> Gregory Woodbury wrote:
> >
> >
> > On Sat, May 28, 2016 at 4:53 PM, Neil Bothwick <neil@××××××××××.uk
> > <mailto:neil@××××××××××.uk>> wrote:
> >
> >     On Sat, 28 May 2016 21:54:09 +0200, Volker Armin Hemmann wrote:
> >
> >     > thanks a lot. My eyes are bleeding.
> >
> >     Serves you right for being daft enough to read it again!
> >
> >     I'd suggest that Alan RTFM for the commands he uses, but that
> >     would be a
> >     waste of keystrokes.
> >
> >
> > I have to agree with ng0
> >
> > WOW!
> >
> > Alan just wants to start it and walk away, as if Gentoo was a binary
> > distribution
> > that handles it all upstream.  He doesn't want to take the time to
> > review what
> > emerge is proposing and see if changes are needed first.
>
> You know what? fuck you.  That's what.
>

You really shouldn't say things like that. Some might consider it
harassment, and others
might take you up on the offer; you never can tell.


>
> The update list it's proposing is 403 packages, or roughly 25% of my
> system.
>

What the...?
Do you have every package there is installed?  The worst updates I have seen
are only 40-50 packages.  403 being 25% implies around 1600 - 1700 packages.
Actually that seems about right, but why are you getting that many updates?
You
may have maladjusted USE flags or keywords to make portage think that many
need an update.  I'm running with ~amd64 set and I check updates once a day.


> > Hey Alan: Gentoo is NOT a start an update and walk away setup. Some human
> > mind needs to be involved if troubles arise.  Also, read make.conf(5)
> > and set up
> > the various variables correctly; PYTHON_SINGLE_TARGET should only have
> > one python version set.
>
> DO YOU SERIOUSLY THINK I'M THAT STUPID??? SERIOUSLY????
>

The output from the script that Dale re-posted clearly shows emerge
complaining
about PYTHON_SINGLE_TARGET being wrong for a dependency expression
in the ebuild involved.  That speaks for itself.

> Furthermore, the current portage doesn't require the revdep-rebuild
> > step because
> > of the @preserved-rebuild set creation.
>
> That missfeature is incompatible with how I use my system. I have not
> reformatted my hard drive in six years.
>

What does reformatting a hard drive have to do with it? I have an
installation that
has been running on one partition since 2011, when I had to build a new
computer
system after a flood.  It does look like I'm going to do a reinstall for
KDE5 Plasma
because too much KDE4 stuff hanging around seems to make the desktop
unstable.  It might take a few hours to do that.


> The principle way I accomplish that is by prohibiting the growth of
> cruft in the system. I cannot tolerate the accumulation of back versions
> anywhere in the system except where absolutely necessary. So if it is
> possible to re-build broken packages against new versions, I demand that
> take place
> as quickly as possible such that the system is left in the most pristine
> and self-consistent state possible. --- secret of immortality, dude. =\
>
> Gentoo used to be superlatively excellent at that.
>
> > In any case, to try and force things through without looking at what
> > problems are occuring
> > is just (excuse my language) batshit crazy stupid.
>
> You
> dumb.
> shit.
>
> You literally have no fucking clue do you?
>

You have no idea...
I have been using UNIX and UNIX-like systems since 1977. I've been involved
in UNIX and Linux for 40 years. I've written drivers, scripts, init systems
and lots
of other stuff, some of which is still hanging around yet.

I guess it tickles your fancy to tell people who know more than you that
they
don't have a "clue" when it is clear that you are ignoring the advice and
guidance
they are offering.

Others in this thread have offered advice and commentary, clearly explaining
why your methods are out-of-whack.  But I do like watching the logs and
builds
scroll by -- one does learn some interesting interactions occasionally.
[For example:
don't build virtualbox with more than -j2 because there is a missing
dependency in
the Makefile.]  For long builds, tailing or lessing the logfiles are easy,
and can be
done in another tab of the terminal program. I also have keep-going in my
default
Emerge options, along with --ask and --verbose; but when a build falters I
can
go look at the saved logfile and see exactly what went wrong, and usually
figure out
how to fix it. Most of the time is is a USE flag mixup, and occasionally a
missing
RDEPEND or DEPEND -- those get reported on Bugzilla.

I add a fair number of USE flags to the profile via make.conf, but some
don't belong
there, but rather in package.use.  I take advantage of the ability for
package.use to
be a directory, and place package specific USE flags in appropriately named
files
within that directory.  Interestingly, the KDE5 Plasma re-install (which is
almost done)
has fewer package specific flags than KDE4. [I prefer KDE and its
flexibility to the
"this is what we say you will use" attitude of GNOME. Also, I keep an LXDE
and XFCE
setup in the mix, just to remain flexible.]

But I am sure you don't care that I don't have the problems you have, even
if I am
using the same basic tools.   It seems that you would rather whine and
complain
that the tool is at fault, instead of heeding the advice that you are not
using it
correctly. Would you also chop firewood with the broadside of an ax?


>
-- 
G.Wolfe Woodbury
redwolfe@×××××.com