| View previous topic :: View next topic |
| Author |
Message |
jxp
n00b
Joined: 25 Dec 2008
Posts: 4
|
 Posted: Fri Dec 26, 2008 12:14 am Post subject: emerge "stable when sufficient; unstable otherwise" |
 |
|
Howdy,
I'm stable and just change the working installation as I need.
But from some packages, I want the newest available version.
When I emerge them using ACCEPT_KEYWORDS=~arch, all of their dependencies are pulled ~unstable, too.
Since many requirements can be resolved using (obviously preferred) stable dependencies, I
- cancel the root emerge
- install/upgrade all dependencies to newest stable versions
- do the final unstable package installation, which in turn
- reemerges some of the just upgraded stable deps to unstables ones.
OK, but manual work == error prone, time consuming.
I'd like a short way to tell emerge:
Install package using ~arch; but with dependencies _mostly harmless_. 
Since I think this problem should be common with everyone using a single unstable ebuild, I would like to know how you're coping with it.
thx in advance
jxp |
|
| Back to top |
|
 |
cyrillic
Watchman
Joined: 19 Feb 2003
Posts: 7313
Location: Groton, Massachusetts USA
|
| Posted: Fri Dec 26, 2008 12:33 am Post subject: Re: emerge "stable when sufficient; unstable otherwise& |
|
|
| jxp wrote: | | Since many requirements can be resolved using (obviously preferred) stable dependencies ... |
Using the latest available version of some package, along with somewhat outdated dependencies might not cause a compile failure, but may introduce subtle problems later on.
My experience is that running a fully ~arch system is not unstable, it is just newer than a "stable" system.
ps. Welcome to the Gentoo Forums. |
|
| Back to top |
|
|
jxp
n00b
Joined: 25 Dec 2008
Posts: 4
|
| Posted: Fri Dec 26, 2008 12:53 am Post subject: |
|
|
Thanks!
This would imply that the root-packages' ebuild dependencies are not coded correctly - they should NEED newer versions of their dependencies then.
As I stated, I don't 'emerge world' for fun.
So after some time, a single necessary unstable package installation has many new dependencies , which I
- don't want to be ~unstable, even if it works for you. Someone who knows better then us has a reason for setting the KEYWORDS that way and I don't want to know really every reason if I can live without.
- would partially downgrade with a following 'emerge world', if I did it.
subtle vs subtle is not easy to decide, so I want the thing to do it. This could be one of the gentoo choices for larry the cow. |
|
| Back to top |
|
|
Mad Merlin
Veteran
Joined: 09 May 2005
Posts: 1155
|
| Posted: Fri Dec 26, 2008 11:55 am Post subject: Re: emerge "stable when sufficient; unstable otherwise& |
|
|
| jxp wrote: | Howdy,
I'm stable and just change the working installation as I need.
But from some packages, I want the newest available version.
When I emerge them using ACCEPT_KEYWORDS=~arch, all of their dependencies are pulled ~unstable, too.
Since many requirements can be resolved using (obviously preferred) stable dependencies, I
- cancel the root emerge
- install/upgrade all dependencies to newest stable versions
- do the final unstable package installation, which in turn
- reemerges some of the just upgraded stable deps to unstables ones.
OK, but manual work == error prone, time consuming.
I'd like a short way to tell emerge:
Install package using ~arch; but with dependencies _mostly harmless_.
Since I think this problem should be common with everyone using a single unstable ebuild, I would like to know how you're coping with it.
thx in advance
jxp |
I think you're saying that you're doing something like this:
| Code: | | ACCEPT_KEYWORDS=~x86 emerge foo |
Which you shouldn't do, it'll cause havoc down the road. Simply keyword the specific packages you want instead, like so:
| Code: | | echo app-editors/vim >>/etc/portage/package.keywords |
Which tells portage to emerge the ~arch version for that package, but only for that package, everything else will still be pulled from arch. For packages with lots of required ~arch deps (like say... ~arch xorg-server), you'll probably find app-portage/autounmask handy.
_________________
Game! - Where the stick is mightier than the sword! |
|
| Back to top |
|
|
cyrillic
Watchman
Joined: 19 Feb 2003
Posts: 7313
Location: Groton, Massachusetts USA
|
| Posted: Fri Dec 26, 2008 2:21 pm Post subject: |
|
|
| jxp wrote: | | Someone who knows better then us has a reason for setting the KEYWORDS that way and I don't want to know really every reason if I can live without. |
Ok, I can understand that.
Since safety is an important concern of yours, you may want to consider running a 100% stable Gentoo system. Not only is this easier to maintain than a mixed system with some testing packages, but you can also be confident that all your applications (and their dependencies) have been adequately tested.
ps. Patience is a virtue, my son.  |
|
| Back to top |
|
|
jxp
n00b
Joined: 25 Dec 2008
Posts: 4
|
| Posted: Fri Dec 26, 2008 5:06 pm Post subject: |
|
|
| Mad Merlin wrote: | | For packages with lots of required ~arch deps (like say... ~arch xorg-server), you'll probably find app-portage/autounmask handy. |
Thanks A LOT, that was what I was looking for.
After a first check, maybe I'll add some functionality using add'l comments in the unmask file for later identification and removal of unmasked sets.
I should have to recheck all the app-portage/ pkgs before asking, as I did some years ago...
cyrillic, 100% stable would be my first choice, but the preamble and reason to post was: using _some_ packages at their newest level (for new functionality or specific fixes I need or fun).
Before using cvs or other source ingestions, I prefer ~-ebuilds.
jxp |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
