[gentoo-dev] NEW ~arch KEYWORDS

[gentoo-dev] NEW ~arch KEYWORDS

[Seemant Kulleen]

[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]

Hi All,

Pursuant to the recently announced news item, (and many of you probably
already know), we have ~arch KEYWORDS in many ebuilds.  The purpose of
this is to allow a stable "profile" for each architecture, without letting
package versions go ridiculously out of date.  So, basically, new packages
will (once the freeze is lifted) and updated versions of current packages
(with the exception of critical and security updates) will get tagged with
~arch for the architectures upon which they were previously marked.

For those of you who are adventurous (yes fans of bleeding edge, I know
you're there, I can see you), please put:

ACCEPT_KEYWORDS="~arch"

(substitute arch for x86, ppc, sparc, sparc64 or alpha, depending on your
hardware platform) and test away. Please report bugs etc so we can have a
relatively updated stable profile too :)



-- 
Seemant Kulleen
Developer and Project Co-ordinator,
Gentoo Linux					http://www.gentoo.org/~seemant

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x225EF866
Key fingerprint = 592A 35F7 09CA FAB4 17B3  6E97 72E6 23CC 225E F866

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] NEW ~arch KEYWORDS

[Evan Read]

On 2002.10.21 10:56 Seemant Kulleen wrote:
> Hi All,
> 
> Pursuant to the recently announced news item, (and many of you
> probably
> already know), we have ~arch KEYWORDS in many ebuilds.  The purpose of
> this is to allow a stable "profile" for each architecture, without
> letting
> package versions go ridiculously out of date.  So, basically, new
> packages
> will (once the freeze is lifted) and updated versions of current
> packages
> (with the exception of critical and security updates) will get tagged
> with
> ~arch for the architectures upon which they were previously marked.
> 
> For those of you who are adventurous (yes fans of bleeding edge, I
> know
> you're there, I can see you), please put:
> 
> ACCEPT_KEYWORDS="~arch"
> 
> (substitute arch for x86, ppc, sparc, sparc64 or alpha, depending on
> your
> hardware platform) and test away. Please report bugs etc so we can
> have a
> relatively updated stable profile too :)


So let me get this straight.  Pacakge masking (and unmasking to test) 
will be a thing of the past?  If one uses that ~arch line, will one 
have the latest packages available?

I am just curious as I have unmasked a heap of Gnome 2 apps and this 
would make my life easier ;)

Thanks

Re: [gentoo-dev] NEW ~arch KEYWORDS

[David Nielsen]

> So let me get this straight.  Pacakge masking (and unmasking to test)
> will be a thing of the past?  If one uses that ~arch line, will one
> have the latest packages available?

As I understand it, no - keywords are used as a means of getting the 
stable/development branching people have been requesting. Global masking will 
still be useful. 
Keywords are a good way of getting around silly stuff like masking perl 
because it fails to compile on PPC, when 90% of the world in on a x86 comp. 
machine.

> I am just curious as I have unmasked a heap of Gnome 2 apps and this
> would make my life easier ;)

depends on Spider and the other GNOME ebuild developers really, but if the 
software is to be considers dangerous and unstable on all platforms global 
masking might be a good idea. So I would expect global masking stay as it is 
for quite some time.

my 2 euro cents

- David

Re: [gentoo-dev] NEW ~arch KEYWORDS

[Spider]

[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]

begin  quote
On Mon, 21 Oct 2002 13:12:23 +0200
David Nielsen <Lovechild@foolclan.com> wrote:

> 
> > I am just curious as I have unmasked a heap of Gnome 2 apps and this
> > would make my life easier ;)
> 
> depends on Spider and the other GNOME ebuild developers really, but if
> the software is to be considers dangerous and unstable on all
> platforms global masking might be a good idea. So I would expect
> global masking stay as it is for quite some time.
> 


Well, here's my take on it:
new sub-branch packages ( 2.0.1 to 2.0.2) will get the ~arch KEYWORD
tagged to them, and then after a week or so when the testing is done on
a wider base, will drop the ~ and become "stable" .

For the new branch 2.1.x  which is highly unstable alpha software you
will still have to dig in package.mask if it ever will be in.  why you
ask? Because once again we will have to re-check all our gnome 2.0.x
packages to not depend on the 2.1 / 2.2 libraries.

(the programs will stay in one slot since they are updated, libraries
coexist, programs overwrite)


so, for the next 2.0.4 or what it will be, it will appear as ~arch,
whereas 2.1 (after freeze) will be digging in package.mask 

//Spider



 
--
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] NEW ~arch KEYWORDS

[cycloon]

[-- Attachment #1: Type: text/plain, Size: 666 bytes --]

On Mon, 2002-10-21 at 15:25, Spider wrote:
> Well, here's my take on it:
> new sub-branch packages ( 2.0.1 to 2.0.2) will get the ~arch KEYWORD
> tagged to them, and then after a week or so when the testing is done on
> a wider base, will drop the ~ and become "stable" .
> 
> For the new branch 2.1.x  which is highly unstable alpha software you
> will still have to dig in package.mask if it ever will be in.  why you
> ask? Because once again we will have to re-check all our gnome 2.0.x
> packages to not depend on the 2.1 / 2.2 libraries.


looks like debian/*BSD-like branching comes to gentoo. Extreme nice.
Go on devs

-- 
www.gentoo-de.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] NEW ~arch KEYWORDS

[Evan Read]

On 2002.10.22 00:17 cycloon wrote:
> On Mon, 2002-10-21 at 15:25, Spider wrote:
> > Well, here's my take on it:
> > new sub-branch packages ( 2.0.1 to 2.0.2) will get the ~arch KEYWORD
> > tagged to them, and then after a week or so when the testing is done
> on
> > a wider base, will drop the ~ and become "stable" .
> >
> > For the new branch 2.1.x  which is highly unstable alpha software
> you
> > will still have to dig in package.mask if it ever will be in.  why
> you
> > ask? Because once again we will have to re-check all our gnome 2.0.x
> > packages to not depend on the 2.1 / 2.2 libraries.
> 
> 
> looks like debian/*BSD-like branching comes to gentoo. Extreme nice.
> Go on devs

I couldn't agree more!  Theirs is a development model that I can 
definately agree with.

Gentoo is looking better everyday.  That, with the binary reference 
platform mentioned in Daniel's article on O'Reilly's, are gonna put 
Gentoo on servers which is great.  I have said it numerous times.  
There is more to Gentoo than just being source based.

Evan.

Re: [gentoo-dev] NEW ~arch KEYWORDS

[Sean]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 21 October 2002 10:17 am, cycloon wrote:
> On Mon, 2002-10-21 at 15:25, Spider wrote:
> > Well, here's my take on it:
> > new sub-branch packages ( 2.0.1 to 2.0.2) will get the ~arch KEYWORD
> > tagged to them, and then after a week or so when the testing is done on
> > a wider base, will drop the ~ and become "stable" .
> >
> > For the new branch 2.1.x  which is highly unstable alpha software you
> > will still have to dig in package.mask if it ever will be in.  why you
> > ask? Because once again we will have to re-check all our gnome 2.0.x
> > packages to not depend on the 2.1 / 2.2 libraries.
>
> looks like debian/*BSD-like branching comes to gentoo. Extreme nice.
> Go on devs

That's a shame ... one of the attractions I had to gentoo was it seemed to 
stay fairly current. Debian is nice and all, but it's a _royal_ pain in the 
rear when you want to start using some current software because of features. 

What good is a great package management scheme when you end up compiling most 
of the software you routinely use anyway.

Sean

- -- 

GPG Public Key available: http://sean.gutenpress.org/sean.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE9tJ13EEGQgHny9sQRAoZ/AKCdyDxwsE/sOVlggr8nw2KYkf+ZuwCdHQu4
DYR0Ks3m55YHzUOqp8dgVoY=
=x7hC
-----END PGP SIGNATURE-----

Re: [gentoo-dev] NEW ~arch KEYWORDS

[cycloon]

[-- Attachment #1: Type: text/plain, Size: 443 bytes --]

On Tue, 2002-10-22 at 02:36, Sean wrote:
> That's a shame ... one of the attractions I had to gentoo was it seemed to 
> stay fairly current. Debian is nice and all, but it's a _royal_ pain in the 
> rear when you want to start using some current software because of features. 

having a stable branch does not need to have such a conservative version
management as debian has. just use the development tree and youre
current as usual

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] NEW ~arch KEYWORDS

[Mark Guertin]

On Tue, 2002-10-22 at 12:24, cycloon wrote:
> On Tue, 2002-10-22 at 02:36, Sean wrote:
> > That's a shame ... one of the attractions I had to gentoo was it seemed to 
> > stay fairly current. Debian is nice and all, but it's a _royal_ pain in the 
> > rear when you want to start using some current software because of features. 
> 
> having a stable branch does not need to have such a conservative version
> management as debian has. just use the development tree and youre
> current as usual

The whole objective with this is to actually provide the users with a
'stable' working setup, but also be quick abot it (unlike debian's
completely seperate trees).  Thing's generally won't live as ~arch for
long at all, just for initial testing phase.  

The more users that pitch in and do testing of these packages, the
faster they will get upgraded to stable :)

Gerk

Re: [gentoo-dev] NEW ~arch KEYWORDS

[Louis-Philippe Brochu]

Mark Guertin wrote:

> The whole objective with this is to actually provide the users with a
> 'stable' working setup, but also be quick abot it (unlike debian's
> completely seperate trees).  Thing's generally won't live as ~arch for
> long at all, just for initial testing phase.

This is great news because it happened a couple times that i emerged a 
new ebuild that wasn't simply working (tightVNC and Postfix comes to 
mind) so i had to revert to the previous version manually. Previously i 
would never schedule an "emerge rsync && emerge world -u" because it 
would often break existing packages and left my system not working properly.

This new feature is really great, however it would be great to be able 
to specify for which packages you want to enable this. You could be 
using stable packages everywhere except for certain softwares which you 
want the latest version and don't care for stability (web browsers or 
games for example).


--
Louis-Philippe Brochu

Re: [gentoo-dev] NEW ~arch KEYWORDS

[Mark Guertin]

On Tue, 2002-10-22 at 14:13, Louis-Philippe Brochu wrote:
> This is great news because it happened a couple times that i emerged a 
> new ebuild that wasn't simply working (tightVNC and Postfix comes to 
> mind) so i had to revert to the previous version manually. Previously i 
> would never schedule an "emerge rsync && emerge world -u" because it 
> would often break existing packages and left my system not working properly.
> 
> This new feature is really great, however it would be great to be able 
> to specify for which packages you want to enable this. You could be 
> using stable packages everywhere except for certain softwares which you 
> want the latest version and don't care for stability (web browsers or 
> games for example).

This can be done very easily... if you don't want to run all the testing
pkgs full time, but simply want one or two pkgs you can do it like this:

ACCEPT_KEYWORDS="~x86" emerge somegame

or alternatively, you can always install an ebuild by referencing the
ebuild file directly (this supercedes keywords, etc)

emerge /usr/portage/app-games/somegame/somegame-0.1.ebuild  (or if it is
in your current working dir, just emerge somegame-0.1.ebuild)

You don't have to include the testing pkgs full time just to get a
couple, there's almost always options if you look hard enough in linux
:)

Gerk

Re: [gentoo-dev] NEW ~arch KEYWORDS

[Louis-Philippe Brochu]

Ok Thanks, i didn't think of this :)


On Tue, 2002-10-22 at 14:21, Mark Guertin wrote:
> This can be done very easily... if you don't want to run all the testing
> pkgs full time, but simply want one or two pkgs you can do it like this:
> 
> ACCEPT_KEYWORDS="~x86" emerge somegame
> 
> or alternatively, you can always install an ebuild by referencing the
> ebuild file directly (this supercedes keywords, etc)
> 
> emerge /usr/portage/app-games/somegame/somegame-0.1.ebuild  (or if it is
> in your current working dir, just emerge somegame-0.1.ebuild)
> 
> You don't have to include the testing pkgs full time just to get a
> couple, there's almost always options if you look hard enough in linux
> :)
> 
> Gerk
> 
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev