1 |
that did it. |
2 |
|
3 |
thanks again! |
4 |
|
5 |
|
6 |
On Tue, 07 Sep 2004 15:45:46 +0100, Kerin Millar |
7 |
<kerin@×××××××××××××××.net> wrote: |
8 |
> |
9 |
> |
10 |
> On Tue, 2004-09-07 at 15:34, Jacob Walcik wrote: |
11 |
> > i've looked in the portage handbook, and i'm digging in the forums |
12 |
> > now, but i can't seem to find a way to do this. |
13 |
> > |
14 |
> > i've got a production postgres database server running gentoo. this |
15 |
> > morning, when updating my desktop (also running gentoo) i noticed that |
16 |
> > a new version of postgres is available. |
17 |
> > |
18 |
> > is there some way to tell the postgres server (and the machines that |
19 |
> > use postgres client libraries to connect to it) to ignore that update? |
20 |
> > i seem to recall there being a mechanism through which you can |
21 |
> > protect certain packages to prevent updates from being applied. |
22 |
> |
23 |
> > glsa-check looks interesting, but doesn't satisfy my requirement of |
24 |
> > packages on production machines only being installed from tested |
25 |
> > binaries built on a dev machine (unless i'm missing something). |
26 |
> |
27 |
> If I recall correctly, it is possible to "pin" a given version of a |
28 |
> package in the world file. But the sensible (by which I mean "more |
29 |
> complete") option is probably to use /etc/portage/package.mask. For |
30 |
> instance: |
31 |
> |
32 |
> # [ ! -e /etc/portage ] && mkdir /etc/portage |
33 |
> # echo ">dev-db/postgresql-7.4.3" >> /etc/portage/package.mask |
34 |
> |
35 |
> would effectively hard-mask any version of postgresql above 7.4.3 (thus, |
36 |
> preventing it from being installed). Be warned though, without |
37 |
> maintenance this strategy may cause errors in time. Consider the |
38 |
> following two theoretical scenarios: |
39 |
> |
40 |
> 1) The 7.4.3 ebuild is eventually pulled from portage, meaning that any |
41 |
> attempted update would fail due to its being masked. |
42 |
> |
43 |
> 2) Another ebuild has an explicit dependency on a newer version of |
44 |
> postgresql. It will be blocked by the fact that the version it wants is |
45 |
> masked. |
46 |
> |
47 |
> Here's an example of how to pin everything on the system: |
48 |
> |
49 |
> # qpkg -I -v -nc | sed -e "s/\(.*\)/>\1/" >> /etc/portage/package.mask |
50 |
> |
51 |
> You could then edit the list according to your tastes. |
52 |
> |
53 |
> Regards, |
54 |
> |
55 |
> --Kerin Francis Millar |
56 |
> |
57 |
> |
58 |
|
59 |
|
60 |
|
61 |
-- |
62 |
jacob walcik |
63 |
jwalcik@×××××.com |