public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Thomas Mueller" <mueller6726@bellsouth.net>
To: gentoo-user@lists.gentoo.org
Subject: Re:  [gentoo-user] necessary use flags
Date: Fri, 26 Jun 2015 05:44:24 +0000	[thread overview]
Message-ID: <649099.96443.bm@smtp116.sbc.mail.gq1.yahoo.com> (raw)
In-Reply-To: 558BBDEE.5010301@gmail.com


> Best way I ever found to learn how things really work under the hood is
> to build a Linux From Scratch and pay close attention to every single step.

> Not that you'd ever actually *use* that system - there's no sane package
> management for a start - but after building an LFS, the content of
> ebuilds in @system starts to make a lot more sense; you can see why some
> of the decisions in the profiles were made; and make.conf now appears in
> a whole new light.

> Then take the valuable lessons from LFS and apply them appropriately to
> using Gentoo. These things are tools and the best workmen are always
> very familiar with their tools as a co-ordinated whole (as opposed to a
> bunch of mish-mash stuff cluttering up a toolbox)

> Alan McKinnon

One could build a system with LFS or CLFS and then adopt one or more package managemant systems such as Gentoo portage, pacman with Arch Build System, voidlinux, etc.

Different package management systems would go to separate installations, separate partitions, of course.

Lack of package management, or actually package management that had no recognition of dependencies, was a large part of what made me not continue with Slackware beyond now-outdated 13.0.

I was spoiled by FreeBSD ports, NetBSD pkgsrc, and Linux distros with package management that recognized dependencies.

Tom



  parent reply	other threads:[~2015-06-26  5:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23 13:05 [gentoo-user] necessary use flgas behrouz khosravi
2015-06-23 13:38 ` Neil Bothwick
2015-06-23 14:45   ` David Haller
2015-06-23 15:31     ` Neil Bothwick
2015-06-23 16:35       ` David Haller
2015-06-23 17:08         ` Neil Bothwick
2015-06-23 18:06           ` David Haller
2015-06-23 17:22         ` [gentoo-user] " James
2015-06-23 19:09           ` David Haller
2015-06-24 10:57 ` [gentoo-user] " Franz Fellner
2015-06-24 11:59   ` behrouz khosravi
2015-06-25  8:25     ` Neil Bothwick
2015-06-24 11:13 ` Alan McKinnon
2015-06-24 11:50   ` Alec Ten Harmsel
2015-06-24 12:09     ` Alec Ten Harmsel
2015-06-24 12:29       ` Alec Ten Harmsel
2015-06-25  4:10     ` [gentoo-user] " »Q«
2015-06-25  8:09     ` [gentoo-user] " Alan McKinnon
2015-06-25  8:27       ` Dale
2015-06-25  8:32         ` Alan McKinnon
2015-06-28  2:16           ` Dale
2015-06-24 12:23   ` behrouz khosravi
2015-06-25  4:25     ` Jc García
2015-06-25  8:38       ` Alan McKinnon
2015-06-25 12:01         ` behrouz khosravi
2015-06-25 12:56           ` Rich Freeman
2015-06-25 15:33             ` Emanuele Rusconi
2015-06-26  5:44         ` Thomas Mueller [this message]
2015-06-25  5:43     ` Walter Dnes
2015-06-25  8:29     ` Alan McKinnon

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=649099.96443.bm@smtp116.sbc.mail.gq1.yahoo.com \
    --to=mueller6726@bellsouth.net \
    --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