From: "Jens Hamacher" <JensHamacher@web.de>
To: <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Patch for mixing stable/unstable
Date: Mon, 3 Mar 2003 17:04:17 +0100 [thread overview]
Message-ID: <004601c2e19e$8b439660$0168a8c0@ntspider> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1515 bytes --]
Hello,
I am relative new to using gentoo.
Coming from debian, I wanted a mixture of testing/unstable, since nobody needs the newest version of every package on his system.
Gentoo gave my troubles when I tried to install two packages from my nvidia graphic card which weren't in stable.
I read there were plans for programming "sticky variables", but I think this is much more complicated then reincluding unstable packages only.
So after looking at the sources of portage 2.0.47-r7 I made this small patch:
- a line in /etc/make.conf with the packages to install "unstable":
UNSTABLE_PKGS="media-video/nvidia-kernel media-video/nvidia-glx"
-a few lines to reinclude the chosen packages:
/usr/lib/python2.2/site-packages/portage.py, line 3395:
cpv=cpv_getkey(mycpv)
if cpv in unstable_include:
match=1
/usr/lib/python2.2/site-packages/portage.py, last line:
unstable_include=settings["UNSTABLE_PKGS"].split()
This seems to work quite good, enabling "update world" and "search" on the newest packages.
One does have to consider the depending packages, if the unstable package requires other unstable packages. But this should be less of a problem with source-based packages than in debian.
And it doesn't check after the architecture at all, so it probably only works for x86 systems. I'll try it with a hash next.
I hope this is a help for some people.
Greetings,
Jens Hamacher
-diff attached-
[-- Attachment #1.2: Type: text/html, Size: 3399 bytes --]
[-- Attachment #2: portage.diff --]
[-- Type: application/octet-stream, Size: 237 bytes --]
3394a3395,3398
> # change Hamacher
> cpv=cpv_getkey(mycpv)
> if cpv in unstable_include:
> match=1
4525a4530
> unstable_include=settings["UNSTABLE_PKGS"].split()
[-- Attachment #3: Type: text/plain, Size: 37 bytes --]
--
gentoo-dev@gentoo.org mailing list
reply other threads:[~2003-03-03 16:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004601c2e19e$8b439660$0168a8c0@ntspider' \
--to=jenshamacher@web.de \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox