Re: [gentoo-user] Naive question
-= 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 or 2005.1?)
Vittorio
-= Eredeti zenet vge (End of original message) =-
Try this:
ls -l /etc/make.profile | sed 's/\// /g' | awk '{print $NF}'
HTH,
Zsoltika
ps: TMTOWTDI of course...
--
Opinions, conclusions and other information in this message that do not
relate to the official business of Online Business Technologies Corp.
shall be understood as neither given nor endorsed by it. In such cases
Online Business Technologies Corp. will not bear the responsibility of
consequences.
If you have received this communication in error, please notify the
system manager immediately by responding to this email and then delete
it from your system.
A levelben foglalt, nem az Online Rt. hivatalos uzletmenetevel kapcsolatos
velemenyek vagy mas informaciok vonatkozasaban az Online Rt. nem vallal
felelosseget.
Amennyiben a level valamely hiba folytan jutott Onhoz, kerjuk, hogy
valaszlevelben azonnal ertesitse a rendszer uzemeltetojet, majd torolje ki
a levelet rendszerebol!
Re: [gentoo-user] Naive question
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 from the profile in
use).
Try this:
ls -l /etc/make.profile | sed 's/\// /g' | awk '{print $NF}'
Just do:
ls -l /etc/make.profile
It will show your current active profile.
Christoph Gysin
--
echo mailto: NOSPAM !#$.'*'|sed 's. ..'|tr * !#:2 [EMAIL PROTECTED]
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Naive question
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 profile.
After an emerge -u world, this doesn't mean anything (apart from the
profile in use).
Try this:
ls -l /etc/make.profile | sed 's/\// /g' | awk '{print $NF}'
Just do:
ls -l /etc/make.profile
It will show your current active profile.
Christoph Gysin
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
- ../usr/portage/profiles/default-linux/x86/2004.3
How come I'm still stuck to 2004.3 and not to 2005.1?
Ciao
Vittorio
--
gentoo-user@gentoo.org mailing list
RE: [gentoo-user] Naive question
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 2004.3 or 2005.1. As all of these files are typically changed as your gentoo system becomes customized (i.e. you edit your /etc/make.conf and files in /etc/portage), I doubt these are used for much. The real question is why do you care what profile your gentoo system was built from? If you've been doing the standard emerge --sync and emerge -uD world, you've already got a system that's beyond whatever the initial 2005.1 profile represents. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Naive question
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 has enabled in the profile), etc. Dave Nebinger wrote: 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 2004.3 or 2005.1. As all of these files are typically changed as your gentoo system becomes customized (i.e. you edit your /etc/make.conf and files in /etc/portage), I doubt these are used for much. The real question is why do you care what profile your gentoo system was built from? If you've been doing the standard emerge --sync and emerge -uD world, you've already got a system that's beyond whatever the initial 2005.1 profile represents. -- gentoo-user@gentoo.org mailing list -- This site uses frames And yet your browser does not. One of these will change. smime.p7s Description: S/MIME Cryptographic Signature
Re: [gentoo-user] Naive question
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 - ../usr/portage/profiles/default-linux/x86/2004.3 How come I'm still stuck to 2004.3 and not to 2005.1? read the answers to your previous message, in particular Chris Gysin's answer. 2004.3 is only your profile, which is a set of defaults that your original system weas built with. forget it, if you have emerge sync'd and then updated your packages, you are up to date. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] naive question about distcc
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 checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i586-pc-linux-gnu-strip... no checking for strip... strip checking for i586-pc-linux-gnu-gcc... gcc ... 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 is it too unworkable and/or risky? I've always wondered about that myself. It's a lot of repetitive work for every install. -- Collins -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] naive question about distcc
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 the fly. All gentoo's ebuild system does really is put a bunch of wrappers around the standard build scripts that each package uses. To do what you ask would require that the EVERY package (or most), to be modified to check a system database of available functions. No such database exists, on all unices, and if it did using it would not be as reliable as actually testing to see if the required function is available. I would not expect this to change. It works amazingly well across an amazing large set of platforms, and frankly, is once of the great portability achievements of the FSF. Lincoln On Sun, 2003-03-30 at 22:14, Collins Richey wrote: 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 checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i586-pc-linux-gnu-strip... no checking for strip... strip checking for i586-pc-linux-gnu-gcc... gcc ... 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 is it too unworkable and/or risky? I've always wondered about that myself. It's a lot of repetitive work for every install. -- Collins -- [EMAIL PROTECTED] mailing list -- Lincoln A. Baxter [EMAIL PROTECTED] -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] naive question about distcc
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 is it too unworkable and/or risky? It's too unworkable, as Lincoln pointed out. What you're asking about is the `./configure` step of install. It lays out a lot of things - which version of this, that, and the other you have, if you are compiling support for an option or disabling it (the Gentoo method for this is use flags), and checks to see if you have the required dependencies. You probably wouldn't see a huge speed increase - after all, how much longer does checking a file for an answer take over checking for a file? - but it would be massively difficult to implement. If you're looking to save time, you ought to look at ccache in addition to distcc. -- Alec Berryman [EMAIL PROTECTED] gpg --keyserver pgp.mit.edu --recv-key DFB366F2 signature.asc Description: This is a digitally signed message part
