[gentoo-user] Re: KDE-meta 4.2 upgrade

2009-02-11 Thread james
Volker Armin Hemmann volkerarmin at googlemail.com writes:


  6. emerge  -DNv kde-meta

  Look plausible? Verbose comments are most welcome.

 just emerge the kde-4.2 set instead of that meta stuff.

Is there a problem with kde-meta-4.2.0 ? I have many different
users asking for many different things, under kde.
Kde-meta make my life simpler. However, if you have
a technical reason not to install kde-meta, for example
too many failed components, then please explain
in some detail Just to save disk space or compile
time, is not a relevant reason for me. I'm interested
in why you say no to kde-meta?


James








Re: [gentoo-user] Re: KDE-meta 4.2 upgrade

2009-02-11 Thread Volker Armin Hemmann
On Mittwoch 11 Februar 2009, james wrote:
 Volker Armin Hemmann volkerarmin at googlemail.com writes:
   6. emerge  -DNv kde-meta
  
   Look plausible? Verbose comments are most welcome.
 
  just emerge the kde-4.2 set instead of that meta stuff.

 Is there a problem with kde-meta-4.2.0 ? I have many different
 users asking for many different things, under kde.
 Kde-meta make my life simpler. However, if you have
 a technical reason not to install kde-meta, for example
 too many failed components, then please explain
 in some detail Just to save disk space or compile
 time, is not a relevant reason for me. I'm interested
 in why you say no to kde-meta?


 James

because meta packages are on their way to be phased out and sets are the way 
to go? Sets are working great? Easier to unmask/keyword?




[gentoo-user] Re: KDE-meta 4.2 upgrade

2009-02-11 Thread James
Alan McKinnon alan.mckinnon at gmail.com writes:

Volker and Alan,

 Finally, try to use sets if possible. The split -meta ebuilds were an ugly 
 hack until sets made it into portage. They were orders of magnitude better 
 than monolithic, but sets are just so much cleaner than -meta. Plus you get 
 to easily define what's in a set if the standard ones don't suit your needs.


OK, I got it, use SETS instead  of kde-meta.
Where do I read up on using SETS?

I see set in the emerge manpage, but it seem, brief.
How do you use the default sets when upgrading to 
kde-4.2.x?

Any examples or further reading?



 I'm finding issues with exiv2, libkeviv2 and stuff that uses it. Like 
 gwenview, okular and krita. But that's the kind of thing that happens 
 occasionally in ~arch

Well this is just one test laptop. The approach is to now put
kde-4.2.0 on this laptop, use it until some comfort is found with
kde-4.2.x and then slowly upgrade the rest of the machine I'm
admin over.


Point well taken about skipping the removal of
kde-meta-3.5.9. Just leave it on the laptop?  I
 thought I had read that that causes problems.
This laptop is my test box, so loosing kde-meta-3.5.9 is no
big deal, as I have another workstation.









Re: [gentoo-user] Re: KDE-meta 4.2 upgrade

2009-02-11 Thread Paul Hartman
On Wed, Feb 11, 2009 at 3:29 PM, James wirel...@tampabay.rr.com wrote:
 Alan McKinnon alan.mckinnon at gmail.com writes:

 Volker and Alan,

 Finally, try to use sets if possible. The split -meta ebuilds were an ugly
 hack until sets made it into portage. They were orders of magnitude better
 than monolithic, but sets are just so much cleaner than -meta. Plus you get
 to easily define what's in a set if the standard ones don't suit your needs.


 OK, I got it, use SETS instead  of kde-meta.
 Where do I read up on using SETS?

 I see set in the emerge manpage, but it seem, brief.
 How do you use the default sets when upgrading to
 kde-4.2.x?

Basically, sets start with @ and you would just emerge like a meta,
emerge @kde-4.2 (or whatever). You can do emerge --list-sets to see
which are available to you. Rather than being meta listed in
/var/lib/portage/world the sets will be listed in
/var/lib/portage/world_sets

You can make your own sets (my stuff or something) and it makes it
easy to get all of your favorite/required packages when setting up a
new system. Just emerge your set and voila :)

The set files are simple, just a text file with a list of package
names inside. You can put your custom sets in /etc/portage/sets I
believe. Overlays can have their own sets (kde-testing has a million
of them).

Lastly, I think you need to be using portage 2.2 in order to have
sets. I'm not sure what version is stable or whatever. I just unmasked
all portage so I'm using whatever the latest one is in the tree.



[gentoo-user] Re: KDE-meta 4.2 upgrade

2009-02-11 Thread james
Paul Hartman paul.hartman+gentoo at gmail.com writes:


 Basically, sets start with @ and you would just emerge like a meta,
 emerge @kde-4.2 (or whatever). You can do emerge --list-sets to see
 which are available to you. Rather than being meta listed in
 /var/lib/portage/world the sets will be listed in
 /var/lib/portage/world_sets

 

Very cool.




I'll give it a shot.


James





Re: [gentoo-user] Re: KDE-meta 4.2 upgrade

2009-02-11 Thread Dale
james wrote:
 Paul Hartman paul.hartman+gentoo at gmail.com writes:


   
 Basically, sets start with @ and you would just emerge like a meta,
 emerge @kde-4.2 (or whatever). You can do emerge --list-sets to see
 which are available to you. Rather than being meta listed in
 /var/lib/portage/world the sets will be listed in
 /var/lib/portage/world_sets
 

  

 Very cool.




 I'll give it a shot.


 James

   

Sorry to butt in here.  I !think! I get what sets does, you add a group
of packages to a file and then when you do the @sets thing, it
emerges/upgrades that group of packages.  I get that part.  I guess from
what I am reading that we the user OR the tree devs can create a sets
file.  So I could create a set called network and put things like Kppp,
ppp, wireshark and all the networky things in there for my use alone.  I
assume that the tree devs can also create a sets file with say all the
KDE packages or maybe all the system packages in it for everybody to
use.  Would that be correct?

I'm going to jump off a cliff here and ask this.  How would I emerge
kde-meta-4.2 and all its friends without using layman or anything, just
a plain emerge @kde-meta and go to bed for a while?  This would be using
the sets feature too.  I am using portage-2.2_rc23 so I should be ready
to go with the new sets feature.

Oh, is there a really good howto somewhere?  Real simple non-geek
speak.  Cool examples would be really nice. I looked around gentoo.org
but nothing really spells it out.  I did find a HUGE thread about it but
still not registering for me.  I need a light bulb moment.  O_O 

Dale

:-)  :-)



Re: [gentoo-user] Re: KDE-meta 4.2 upgrade

2009-02-11 Thread Alan McKinnon
On Thursday 12 February 2009 07:01:36 Dale wrote:

 Sorry to butt in here.  I !think! I get what sets does, you add a group
 of packages to a file and then when you do the @sets thing, it
 emerges/upgrades that group of packages.  I get that part.  I guess from
 what I am reading that we the user OR the tree devs can create a sets
 file.  

Yes. The old split -meta ebuilds were a stop-gap hack while waiting for set 
functionality (the devs said as much in the kde split-ebuild handbook page) 
but required that a full-blown ebuild be written. Which then had to be 
manifested and either inserted in the tree or an overlay. i.e. 
waay too complex for what is really just a simple list.

 So I could create a set called network and put things like Kppp, 
 ppp, wireshark and all the networky things in there for my use alone.  

Yes

 I 
 assume that the tree devs can also create a sets file with say all the
 KDE packages or maybe all the system packages in it for everybody to
 use.  Would that be correct?

Yes. 

 I'm going to jump off a cliff here and ask this.  How would I emerge
 kde-meta-4.2 and all its friends without using layman or anything, just
 a plain emerge @kde-meta and go to bed for a while?  This would be using
 the sets feature too.  I am using portage-2.2_rc23 so I should be ready
 to go with the new sets feature.

Forget about anything with -meta in it's name if you want to use sets. As I 
said above, -meta ebuilds are a hack and an ugly one to boot (but useful 
nonetheless). Create a file called say /etc/portage/sets/dale_stuff and run

emerge -av @dale_stuff

Go to bed. To get all the kde stuff, I *think* that easiest would be to ask 
someone using kde-testing to mail you a copy of the set file included there. 
Or you could make one by hand with ls,grep,sed,awk and friends.

 Oh, is there a really good howto somewhere?  Real simple non-geek
 speak.  Cool examples would be really nice. I looked around gentoo.org
 but nothing really spells it out.  I did find a HUGE thread about it but
 still not registering for me.  I need a light bulb moment.  O_O

There isn't much in the way of docs. I read a blog post from one of the devs 
recently but have no idea where it is. I'll have a look.

It would appear from some code snippets I saw there that you can even do nifty 
things like subtract one set from another. Say you wanted all of kde except 
three specific apps. Put those three in a set file, let's call it 
kde_exclude, and run some command along the lines of

emerge @k...@kde_exclude

portage will subtract the exclude file from the big one and merge just the 
difference. Cool, hey?

-- 
alan dot mckinnon at gmail dot com



Re: [gentoo-user] Re: KDE-meta 4.2 upgrade

2009-02-11 Thread Dale
Alan McKinnon wrote:
 On Thursday 12 February 2009 07:01:36 Dale wrote:

   
 Sorry to butt in here.  I !think! I get what sets does, you add a group
 of packages to a file and then when you do the @sets thing, it
 emerges/upgrades that group of packages.  I get that part.  I guess from
 what I am reading that we the user OR the tree devs can create a sets
 file.  
 

 Yes. The old split -meta ebuilds were a stop-gap hack while waiting for set 
 functionality (the devs said as much in the kde split-ebuild handbook page) 
 but required that a full-blown ebuild be written. Which then had to be 
 manifested and either inserted in the tree or an overlay. i.e. 
 waay too complex for what is really just a simple list.

   
 So I could create a set called network and put things like Kppp, 
 ppp, wireshark and all the networky things in there for my use alone.  
 

 Yes

   
 I 
 assume that the tree devs can also create a sets file with say all the
 KDE packages or maybe all the system packages in it for everybody to
 use.  Would that be correct?
 

 Yes. 

   
 I'm going to jump off a cliff here and ask this.  How would I emerge
 kde-meta-4.2 and all its friends without using layman or anything, just
 a plain emerge @kde-meta and go to bed for a while?  This would be using
 the sets feature too.  I am using portage-2.2_rc23 so I should be ready
 to go with the new sets feature.
 

 Forget about anything with -meta in it's name if you want to use sets. As I 
 said above, -meta ebuilds are a hack and an ugly one to boot (but useful 
 nonetheless). Create a file called say /etc/portage/sets/dale_stuff and run

 emerge -av @dale_stuff

 Go to bed. To get all the kde stuff, I *think* that easiest would be to ask 
 someone using kde-testing to mail you a copy of the set file included there. 
 Or you could make one by hand with ls,grep,sed,awk and friends.

   
 Oh, is there a really good howto somewhere?  Real simple non-geek
 speak.  Cool examples would be really nice. I looked around gentoo.org
 but nothing really spells it out.  I did find a HUGE thread about it but
 still not registering for me.  I need a light bulb moment.  O_O
 

 There isn't much in the way of docs. I read a blog post from one of the devs 
 recently but have no idea where it is. I'll have a look.

 It would appear from some code snippets I saw there that you can even do 
 nifty 
 things like subtract one set from another. Say you wanted all of kde except 
 three specific apps. Put those three in a set file, let's call it 
 kde_exclude, and run some command along the lines of

 emerge @k...@kde_exclude

 portage will subtract the exclude file from the big one and merge just the 
 difference. Cool, hey?

   

Cool.  Thanks for the info.  Nice to know I understood some things
correctly.  Even a dead clock is right twice a day.  o_O

Dale

:-)  :-)