public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joseph <syscon780@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: gentoo
Date: Tue, 16 Sep 2014 14:23:24 -0600	[thread overview]
Message-ID: <20140916202324.GA7543@syscon7> (raw)
In-Reply-To: <loom.20140916T211948-772@post.gmane.org>

On 09/16/14 19:58, James wrote:
[snip]
>
>Folks that work on precise computer problems are often "raw" with
>one another. "Sarcasm" is an ointment that soothes the pain
>of running Gentoo. Verbal abuse develops "thick skin" and most
>here on Gentoo User have "thick skin", imho.  Devs on this
>list often question the gentoo-user base to ferret out if they
>need to modify docs, codes or semantics at Gentoo, or if the user
>needs. Sometime it does resemble a court room.
>
> "Alan's school of admin abuse" type of treatment to motivate
>an excellent user base is not uncommon.
>
>That said, the amount of questions and bandwidth you have incurred
>on this group, does warrant administrative incursion into you
>admin policies, imho. Maybe, just maybe, folks actually care
>that you are wisely successful with Gentoo?
>
>For example since you are distributing, you really need to keep
>binaries packages on at least one system. I nuked python, some
>years ago. It was only the files on another similar system that
>prevent me form a new installation of the system.
>
>Besides, I rather think you are being "groomed" to become a gentoo
>dev, so you can abuse the rest of of (gentoo users) commoners?
>
>
>hth,
>James

Thank for suggestions, yes I usually keep the binaries for as long as I have enough room on "/" :-)
If I'm short on space I periodically nuke them. I've manged to keep the system going for the last 10-years
and keep my own help-file.txt (notes) how to solve certain problem (but not all :-/)

I sometime clean the distribution files with this command (I'm sure there might be a better way).
-----------------
cd /usr/portage/distfiles

and run this command:
(emerge -epf world  2>&1 | perl -ne '$f=join("\n", m@\w://[^\s]+/([^\s]+)@g); print "$f\n" if $f' | sort -u; ls -f) | sort | uniq -c | perl -ane 'print "$F[1]\n" if 
$F[0]==1 && -f $F[1]' | xargs rm -f
------------------

Regarding keeping the binaries, I'll need to learn how to install compiled binaries from another box.  Never, had a chance to do it yet.

-- 
Joseph


  reply	other threads:[~2014-09-16 20:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16  4:29 [gentoo-user] gentoo Joseph
2014-09-16  5:23 ` [gentoo-user] removing preserve rebuild Joseph
2014-09-16 10:45   ` Tomas Mozes
2014-09-16 12:01   ` Neil Bothwick
2014-09-16 12:20   ` Alan McKinnon
2014-09-16 13:52     ` Joseph
2014-09-16 14:44       ` Alan McKinnon
2014-09-16 14:18 ` [gentoo-user] Re: gentoo James
2014-09-16 15:02   ` Joseph
2014-09-16 15:57     ` J. Roeleveld
2014-09-16 18:05       ` Joseph
2014-09-16 19:11         ` Alan McKinnon
2014-09-16 19:38           ` Joseph
2014-09-16 19:58         ` James
2014-09-16 20:23           ` Joseph [this message]
2014-09-16 20:42             ` Alan McKinnon
2014-09-16 21:28             ` James
     [not found] <200412051508.59017.dlw@hei.net>
2004-12-06  0:24 ` Gabriel M. Beddingfield
2004-12-06  5:14   ` Ow Mun Heng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140916202324.GA7543@syscon7 \
    --to=syscon780@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox