Having updated gentoo frequently how can I know what version of gentoo I'm
using (2004.4 or 2005.1?)
Vittorio
--
gentoo-user@gentoo.org mailing list
-= Eredeti zenet (Original message) =-
Dtum (Date): Thu, 3 Mar 2005 13:18:31 +
Kld (From): Vittorio [EMAIL PROTECTED]
Cmzett (To): [EMAIL PROTECTED]
Trgy (Subject): [gentoo-user] Naive question
Having updated gentoo frequently how can I know what version of gentoo I'm
using (2004.4
Botykai Zsolt wrote:
Having updated gentoo frequently how can I know what version of gentoo I'm
using (2004.4 or 2005.1?)
There is no such thing as a gentoo version. 200x.y is simply the version of the
install stages and the profile.
After an emerge -u world, this doesn't mean anything (apart
Alle 12:53, giovedì 3 marzo 2005, Christoph Gysin ha scritto:
Botykai Zsolt wrote:
Having updated gentoo frequently how can I know what version of gentoo
I'm using (2004.4 or 2005.1?)
There is no such thing as a gentoo version. 200x.y is simply the version of
the install stages and the
Take a look at the contents of /etc/make.profile. There's really not much
in there outside of (from what I can see) files containing use flags and
package masks.
If I had to venture a guess, I'd say it was the default values used to
construct the base system from your initial install, whether
I believe that they are the default settings even after customization,
/etc/make.conf just overrides them. If you didn't have USE flags in
there, than nothing would be declared, but there are default USE flags
put into use, and you can do your customization based on them (disabling
what Gentoo
On Thu, 3 Mar 2005 18:37:39 +
Vittorio wrote:
I'm somewhat confused!
Just yesterday I issued an emerge --rsync, fixpackages, then
emerge -ubD world
Issuing now ls -l /etc/make.profile I get
lrwxrwxrwx 1 root root 48 4 gen 18:46 /etc/make.profile
-
I've noticed that when I do makes, a lot of time is spent by the system
checking lots of stuff:
...
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for
On Sun, 30 Mar 2003 22:09:24 -0500
Jeremy Schneider [EMAIL PROTECTED] wrote:
I've noticed that when I do makes, a lot of time is spent by the
system checking lots of stuff:
...
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
It is obvious you have never built any of these packages by hand.
Almost all OSS packages today use the GNU configure scripts to configure
them for building on a BUNCH of difference platforms. Linux being just
one. These scripts build the actual makefiles that are used to compile
the package on
On Sun, 2003-03-30 at 21:09, Jeremy Schneider wrote:
It occurs to me that these things don't change very often on my system, and
that the answer to these checks could be cached, perhaps associated with a
hash or date of certain config files, such as make.conf. Does this make any
sense, or
11 matches
Mail list logo
