[gentoo-user] Updated gentoo systems and fresh installs

2006-03-13 Thread Trenton Adams
Hi guys,

Is there a difference between the two?  I have 2005.1 installed.  As
I've always understood it, my system will now always be up-to-date, as
long as I keep updating it.  Is 2006.0 any different than 2005.1 after
the system has been installed?

I'm just curious, because I have to install gentoo on a notebook, but
I want package compatibility with my server.

Thanks.

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Updated gentoo systems and fresh installs

2006-03-13 Thread Hemmann, Volker Armin
On Monday 13 March 2006 21:54, Trenton Adams wrote:
 Hi guys,

 Is there a difference between the two?  I have 2005.1 installed.  As
 I've always understood it, my system will now always be up-to-date, as
 long as I keep updating it.  Is 2006.0 any different than 2005.1 after
 the system has been installed?

no

an up to date gentoo is not different from an up to date release. The 
installation is propably even more actual, than the latest release.


 I'm just curious, because I have to install gentoo on a notebook, but
 I want package compatibility with my server.

there won't be problems. After the an emerge sync, emerge -u world, both are 
more or less identical.
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Updated gentoo systems and fresh installs

2006-03-13 Thread Daniel da Veiga
On 3/13/06, Trenton Adams [EMAIL PROTECTED] wrote:
 Hi guys,

 Is there a difference between the two?  I have 2005.1 installed.  As
 I've always understood it, my system will now always be up-to-date, as
 long as I keep updating it.  Is 2006.0 any different than 2005.1 after
 the system has been installed?

No, you're given options while you update with emerge -uD world, you
can compile GCC 3.4.5 but not use it till you gcc-config it. You
download and unpack the latest kernel, but you CHOOSE to compile it
and change versions. If you always choose to upgrade this slotted
packages, you'll always have the latest Gentoo as a whole.

The Gentoom 2006.0 comes with some of this packages already upgraded
to the latest versions, that's the only difference, a install of
2005.1 would have a lot of compiling and upgrading and maybe some
configuration to change between versions, other than that, you'll
always end up with the latest Gentoo on both machines (if you choose
to).


 I'm just curious, because I have to install gentoo on a notebook, but
 I want package compatibility with my server.

 Thanks.

 --
 gentoo-user@gentoo.org mailing list




--
Daniel da Veiga
Computer Operator - RS - Brazil
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
--END GEEK CODE BLOCK--

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Updated gentoo systems and fresh installs

2006-03-13 Thread gentuxx
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Trenton Adams wrote:

Hi guys,

Is there a difference between the two? I have 2005.1 installed. As
I've always understood it, my system will now always be up-to-date, as
long as I keep updating it. Is 2006.0 any different than 2005.1 after
the system has been installed?

I'm just curious, because I have to install gentoo on a notebook, but
I want package compatibility with my server.

Thanks.

As I understand it, this is essentially true.  As long as you continue
to update your system, it will remain up to a date.  However,
depending upon your architecture, there may be packages that are
masked by profile.  I've really only seen this on SPARC systems, but
others may pop up as well.  For example, the 2.6 kernel is masked in
the 2005.1 SPARC profile, but not in the 2006.0 profile.  I am still
running the 2005.0 on my P4 x86 system, and haven't run into any
profile-related issues.

- --
gentux
echo hfouvyAdpy/ofu | perl -pe 's/(.)/chr(ord($1)-1)/ge'

gentux's gpg fingerprint == 34CE 2E97 40C7 EF6E EC40  9795 2D81 924A
6996 0993
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (GNU/Linux)

iD8DBQFEFeLGLYGSSmmWCZMRAgG4AKCb/OTawnb9CszNr8EyCZhmn8NbiwCfed7A
tHihV+1ac3E8EcySPKJNZDM=
=yklO
-END PGP SIGNATURE-

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Updated gentoo systems and fresh installs

2006-03-13 Thread Boyd Stephen Smith Jr.
On Monday 13 March 2006 14:54, Trenton Adams [EMAIL PROTECTED] 
wrote about '[gentoo-user] Updated gentoo systems and fresh installs':
 Is there a difference between the two?  I have 2005.1 installed.  As
 I've always understood it, my system will now always be up-to-date, as
 long as I keep updating it.  Is 2006.0 any different than 2005.1 after
 the system has been installed?

Not very.  Some packages are masked by the profile so changing profiles 
will change what packages are installed, sometimes.

I'm assuming you are using default-linux/x86/2005.1 and thinking about 
moving to default-linux/x86/2006.0 (there are equivalents for most archs, 
and probably some of the sub-profiles).  If that's the case we see that:
$ diff -u 2005.1 2006.0
diff -u 2005.1/make.defaults 2006.0/make.defaults
--- 2005.1/make.defaults2005-11-16 11:06:03.0 -0600
+++ 2006.0/make.defaults2006-01-31 17:06:15.0 -0600
@@ -1,5 +1,9 @@
-# 
$Header: 
/var/cvsroot/gentoo-x86/profiles/default-linux/x86/2005.1/make.defaults,v 
1.5 2005/11/16 17:00:36 wolf31o2 Exp $
+# 
$Header: 
/var/cvsroot/gentoo-x86/profiles/default-linux/x86/2006.0/make.defaults,v 
1.6 2006/01/31 23:03:05 wolf31o2 Exp $

-USE=alsa apm arts avi bitmap-fonts cups eds emboss encode fortran 
foomaticdb gdbm gif gnome gpm gstreamer gtk gtk2 imlib jpeg kde libg++ 
libwww mad mikmod motif mp3 mpeg ogg oggvorbis opengl oss pdflib png qt 
quicktime sdl spell truetype truetype-fonts type1-fonts vorbis X xml2 xmms 
xv
+# This is currently commented so that the stage1 tarball can also be used 
to
+# build no-nptl systems.
+#STAGE1_USE=nptl
+
+USE=alsa apache2 apm arts avi cups eds emboss encode esd foomaticdb gdbm 
gif gnome gpm gstreamer gtk gtk2 imlib jpeg kde libg++ libwww mad mikmod 
motif mp3 mpeg nptl ogg opengl oss pdflib png qt quicktime sdl spell 
truetype udev vorbis X xml xmms xv
diff -u 2005.1/packages 2006.0/packages
--- 2005.1/packages 2005-07-07 16:09:07.0 -0500
+++ 2006.0/packages 2006-01-18 15:19:57.0 -0600
@@ -1,6 +1,6 @@
-# 
$Header: /var/cvsroot/gentoo-x86/profiles/default-linux/x86/2005.1/packages,v 
1.2 2005/07/07 20:11:37 wolf31o2 Exp $
+# 
$Header: /var/cvsroot/gentoo-x86/profiles/default-linux/x86/2006.0/packages,v 
1.1 2006/01/18 21:19:57 wolf31o2 Exp $
Only in 2005.1: vserver

(I stripped out the context lines, but things aren't wrapping correctly, so 
that my be a little hard to read.)

ANYWAY, looks to me like vserver support is no longer available as a 
sub-profile, probably replaced or superceeded by default-linux/x86/vserver 
and that the default USE flags changed by adding apache2, esd, nptl, udev, 
and xml and removing bitmap-fonts, fortran, oggvorbis, truetype-fonts, 
type1-fonts, and xml2.

nptl and udev you were probably already using, esd maybe not and it'll 
probably bring in a dependency or two.  I betting xml2 has just gone away, 
in favor of xml.  oggvorbis should have also gone away since there's no 
special libraries necessary to handle vorbis data in the ogg wrapper other 
that the ability to handle vorbis data (which can be in another wrapper, 
like matroska) and open ogg wrappers (which can contain other data like 
speex or theora).  Changing the fortran flag will probably make your gcc 
recompile, unless you already had it turned off; I don't actually compile 
fortran, do you?  I'm not really sure what's up with the fonts options, 
but it does make sense to not default to ALL types of fonts.  The biggest 
change is the apache2 flag, so you may want to disable that is you do go 
with 2006.0

 I'm just curious, because I have to install gentoo on a notebook, but
 I want package compatibility with my server.

Do you mean you want to be able to use binary packages from the server, so 
that you don't have to compile on the notebook?  If so, you probably want 
to keep both make.conf, make.profile, and /etc/portage identical.  (If USE 
flags are different, a binary package will not be used.)

-- 
If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability.
-- Gentoo Developer Ciaran McCreesh
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Updated gentoo systems and fresh installs

2006-03-13 Thread Trenton Adams
Thanks everyone.

Just so you'll all have an extra tidbit of knowledge.  A co-worker
mentioned one other thing that could be a problem, that no one else
mentioned.  If you have not yet upgraded GCC on an old version, then
use an up-to-date installation with a newer GCC, you will have binary
incompatibilities with your package build system.

On 3/13/06, Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote:
 On Monday 13 March 2006 14:54, Trenton Adams [EMAIL PROTECTED]
 wrote about '[gentoo-user] Updated gentoo systems and fresh installs':
  Is there a difference between the two?  I have 2005.1 installed.  As
  I've always understood it, my system will now always be up-to-date, as
  long as I keep updating it.  Is 2006.0 any different than 2005.1 after
  the system has been installed?

 Not very.  Some packages are masked by the profile so changing profiles
 will change what packages are installed, sometimes.

 I'm assuming you are using default-linux/x86/2005.1 and thinking about
 moving to default-linux/x86/2006.0 (there are equivalents for most archs,
 and probably some of the sub-profiles).  If that's the case we see that:
 $ diff -u 2005.1 2006.0
 diff -u 2005.1/make.defaults 2006.0/make.defaults
 --- 2005.1/make.defaults2005-11-16 11:06:03.0 -0600
 +++ 2006.0/make.defaults2006-01-31 17:06:15.0 -0600
 @@ -1,5 +1,9 @@
 -#
 $Header: 
 /var/cvsroot/gentoo-x86/profiles/default-linux/x86/2005.1/make.defaults,v
 1.5 2005/11/16 17:00:36 wolf31o2 Exp $
 +#
 $Header: 
 /var/cvsroot/gentoo-x86/profiles/default-linux/x86/2006.0/make.defaults,v
 1.6 2006/01/31 23:03:05 wolf31o2 Exp $

 -USE=alsa apm arts avi bitmap-fonts cups eds emboss encode fortran
 foomaticdb gdbm gif gnome gpm gstreamer gtk gtk2 imlib jpeg kde libg++
 libwww mad mikmod motif mp3 mpeg ogg oggvorbis opengl oss pdflib png qt
 quicktime sdl spell truetype truetype-fonts type1-fonts vorbis X xml2 xmms
 xv
 +# This is currently commented so that the stage1 tarball can also be used
 to
 +# build no-nptl systems.
 +#STAGE1_USE=nptl
 +
 +USE=alsa apache2 apm arts avi cups eds emboss encode esd foomaticdb gdbm
 gif gnome gpm gstreamer gtk gtk2 imlib jpeg kde libg++ libwww mad mikmod
 motif mp3 mpeg nptl ogg opengl oss pdflib png qt quicktime sdl spell
 truetype udev vorbis X xml xmms xv
 diff -u 2005.1/packages 2006.0/packages
 --- 2005.1/packages 2005-07-07 16:09:07.0 -0500
 +++ 2006.0/packages 2006-01-18 15:19:57.0 -0600
 @@ -1,6 +1,6 @@
 -#
 $Header: /var/cvsroot/gentoo-x86/profiles/default-linux/x86/2005.1/packages,v
 1.2 2005/07/07 20:11:37 wolf31o2 Exp $
 +#
 $Header: /var/cvsroot/gentoo-x86/profiles/default-linux/x86/2006.0/packages,v
 1.1 2006/01/18 21:19:57 wolf31o2 Exp $
 Only in 2005.1: vserver

 (I stripped out the context lines, but things aren't wrapping correctly, so
 that my be a little hard to read.)

 ANYWAY, looks to me like vserver support is no longer available as a
 sub-profile, probably replaced or superceeded by default-linux/x86/vserver
 and that the default USE flags changed by adding apache2, esd, nptl, udev,
 and xml and removing bitmap-fonts, fortran, oggvorbis, truetype-fonts,
 type1-fonts, and xml2.

 nptl and udev you were probably already using, esd maybe not and it'll
 probably bring in a dependency or two.  I betting xml2 has just gone away,
 in favor of xml.  oggvorbis should have also gone away since there's no
 special libraries necessary to handle vorbis data in the ogg wrapper other
 that the ability to handle vorbis data (which can be in another wrapper,
 like matroska) and open ogg wrappers (which can contain other data like
 speex or theora).  Changing the fortran flag will probably make your gcc
 recompile, unless you already had it turned off; I don't actually compile
 fortran, do you?  I'm not really sure what's up with the fonts options,
 but it does make sense to not default to ALL types of fonts.  The biggest
 change is the apache2 flag, so you may want to disable that is you do go
 with 2006.0

  I'm just curious, because I have to install gentoo on a notebook, but
  I want package compatibility with my server.

 Do you mean you want to be able to use binary packages from the server, so
 that you don't have to compile on the notebook?  If so, you probably want
 to keep both make.conf, make.profile, and /etc/portage identical.  (If USE
 flags are different, a binary package will not be used.)

 --
 If there's one thing we've established over the years,
 it's that the vast majority of our users don't have the slightest
 clue what's best for them in terms of package stability.
 -- Gentoo Developer Ciaran McCreesh
 --
 gentoo-user@gentoo.org mailing list



-- 
gentoo-user@gentoo.org mailing list