gnome3 gentoo

knfpndc: well if you want gnome3, you need to allow unstable on certain packages... using the configs in that dir is safer & easier to rollback that going full unstable

<knfpndc> iamben layman -a gnome supposed to change emerge gnome to overlay repoz and emerge gnome3
[07:09] <+iamben> knfpndc: the gnome3 packags are still not marked stable

knfpndc: autounmask will probably pull in more unstable stuff than the premade keywords file from the overlay
<+iamben> knfpndc: i assume that's what you're wanting, right?
<+iamben> knfpndc: what does "emerge =gnome-3*" say?
<+iamben> knfpndc: yes, emerge sees your gnome overlay but the ebuilds are not marked stable.
 <+iamben> knfpndc: have you ever used /etc/portage/package.keywords?
<+iamben> knfpndc: if you create /etc/portage/package.keywords/ as a dir, you can copy or symlink /var/lib/layman/gnome/status/portage-configs/package.keywords.gnome3 inside there, and it will allow unstable keywords for the required pkgs for gnome3
 <knfpndc> iamben: copy or symlink what exactly?
[07:25] <+iamben> knfpndc: copy or symlink that package.gnome.keywords file (which is provided in the overlay) into /etc/portage/package.keywords/
[07:25] <+iamben> the symlink is good so it stays updated as the overlay maintainers modify the keywords file
<knfpndc> iamben: So we are going with symlink; but i am still fuzzy in the details
[07:26] <+iamben> "ln -s /var/lib/layman/gnome/status/portage-configs/package.keywords.gnome3 /etc/portage/package.keywords/"
<knfpndc> where could i find package.gnome.keywords and how could i do symlink
<knfpndc> iamben: I jsut add echo "source /var/lib/layman/make.conf" >> /etc/make.conf" after layman -a gnome
<+iamben> knfpndc: then the keywords file is where i said


The following mask changes are necessary to proceed:
#required by gnome-base/gnome-3.0.0, required by gnome (argument)
# /usr/portage/profiles/package.mask:
# Nirbheek Chauhan <nirbheek@gentoo.org> (10 Jun 2009)
# Several feature regressions that will make our users
# go on a witchhunt if unmasked
# * No XDMCP connection UI
# * No configuration/theming support
# * No support for auth backends other than PAM
# * Many more...
>=gnome-base/gdm-3.0.4-r1

<richiefrich> knfpndc: ^
[17:17] <keeperofdakeys> knfpndc: it isn't a keyword, you need to put "=gnome-base/gnome-3.0.0" in /etc/portage/package.unmask
[17:18] <keeperofdakeys> oh, wait, sorry, I'm wrong
[17:18] <keeperofdakeys> it is gdm
[17:18] <keeperofdakeys> you need to put "gnome-base/gdm" in package.unmask
[17:18] <richiefrich> right he needs to unmask gdm
[17:18] <keeperofdakeys> but, yeah, the overlay should have done that


 knfpndc: in some very limited cases, an actual USE flag can be masked by your profile.  when the feature is known to be broken or risky on your setup.  in this case, you do need to unmask it to get gnome3 (i assume that's what youre going for)



knfpndc: well if you want gnome3, you need to allow unstable on certain packages... using the configs in that dir is safer & easier to rollback that going full unstable

<knfpndc> iamben layman -a gnome supposed to change emerge gnome to overlay repoz and emerge gnome3
[07:09] <+iamben> knfpndc: the gnome3 packags are still not marked stable

knfpndc: autounmask will probably pull in more unstable stuff than the premade keywords file from the overlay
<+iamben> knfpndc: i assume that's what you're wanting, right?
<+iamben> knfpndc: what does "emerge =gnome-3*" say?
<+iamben> knfpndc: yes, emerge sees your gnome overlay but the ebuilds are not marked stable.
 <+iamben> knfpndc: have you ever used /etc/portage/package.keywords?
<+iamben> knfpndc: if you create /etc/portage/package.keywords/ as a dir, you can copy or symlink /var/lib/layman/gnome/status/portage-configs/package.keywords.gnome3 inside there, and it will allow unstable keywords for the required pkgs for gnome3
 <knfpndc> iamben: copy or symlink what exactly?
[07:25] <+iamben> knfpndc: copy or symlink that package.gnome.keywords file (which is provided in the overlay) into /etc/portage/package.keywords/
[07:25] <+iamben> the symlink is good so it stays updated as the overlay maintainers modify the keywords file
<knfpndc> iamben: So we are going with symlink; but i am still fuzzy in the details
[07:26] <+iamben> "ln -s /var/lib/layman/gnome/status/portage-configs/package.keywords.gnome3 /etc/portage/package.keywords/"
<knfpndc> where could i find package.gnome.keywords and how could i do symlink
<knfpndc> iamben: I jsut add echo "source /var/lib/layman/make.conf" >> /etc/make.conf" after layman -a gnome
<+iamben> knfpndc: then the keywords file is where i said


The following mask changes are necessary to proceed:
#required by gnome-base/gnome-3.0.0, required by gnome (argument)
# /usr/portage/profiles/package.mask:
# Nirbheek Chauhan <nirbheek@gentoo.org> (10 Jun 2009)
# Several feature regressions that will make our users
# go on a witchhunt if unmasked
# * No XDMCP connection UI
# * No configuration/theming support
# * No support for auth backends other than PAM
# * Many more...
>=gnome-base/gdm-3.0.4-r1

<richiefrich> knfpndc: ^
[17:17] <keeperofdakeys> knfpndc: it isn't a keyword, you need to put "=gnome-base/gnome-3.0.0" in /etc/portage/package.unmask
[17:18] <keeperofdakeys> oh, wait, sorry, I'm wrong
[17:18] <keeperofdakeys> it is gdm
[17:18] <keeperofdakeys> you need to put "gnome-base/gdm" in package.unmask
[17:18] <richiefrich> right he needs to unmask gdm
[17:18] <keeperofdakeys> but, yeah, the overlay should have done that

 emerge -pv pygobject

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] dev-python/pygobject-2.28.6  USE="cairo -doc -examples (-introspection) -libffi -test" 0 kB

<+iamben> knfpndc: in some very limited cases, an actual USE flag can be masked by your profile.  when the feature is known to be broken or risky on your setup.  in this case, you do need to unmask it to get gnome3 (i assume that's what youre going for)


knfpndc: unmasking USE flags is quite different from other masks though, you create the use.mask file with -flag to unmask it.  and it goes in /etc/portage/profile/, note the profile subdirr

<+iamben> knfpndc: when emerge shows a flag as (-flag), it's masked

[20:44] <+iamben> and you will need to create that dir & file yourself
[20:44] <+iamben> but no, there is no use.unmask
[20:44] == shal3r [~shal3r@office.gold.lv] has quit [Ping timeout: 255 seconds]
[20:44] <+iamben> you just put -flag in your own use.mask (wierd, i know)

<+iamben> mkdir -p /etc/portage/profile/ && echo "-introspection" >> /etc/portage/profile/use.mask



Note: the iam specified that when -p emerge said -flag it means that the flag is masked and u should Do above. (- introspection aslo in blue means it is masked by the profile)