From: "Ryan Sims" <rwsims@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how do I keep package from being updated?
Date: Thu, 11 Jan 2007 13:09:47 -0500 [thread overview]
Message-ID: <64e8d2f20701111009s3f3a4ab9ob57531ed343ac6e8@mail.gmail.com> (raw)
In-Reply-To: <17830.31298.79299.518954@ccs.covici.com>
On 1/11/07, John covici <covici@ccs.covici.com> wrote:
> If I have two versions on the systems, how would apache and the cli
> pick what version they are going to use?
I think there was just a thread on top-posting, btw.
IIRC, you pass "-DPHP5" or "-DPHP4" to apache in /etc/conf.d/apache
(or possibly /etc/conf.d/apache2). As for cli, I'm not sure, I
haven't used it much.
> on Thursday 01/11/2007 Hans-Werner Hilse(hilse@web.de) wrote
> > Hi,
> >
> > On Thu, 11 Jan 2007 11:38:38 -0500
> > John covici <covici@ccs.covici.com> wrote:
> >
> > > OK, I did put my php version in the /etc/portage/package.mask, but it
> > > still wants to install a new major version -- curiously it says ebuild
> > > -ns rather than just -n or -u. I put the following line in there
> > > =dev-lang/php-4.4.4-r8
> >
> > you don't want to mask the currently installed version (=), but rather the
> > versions "greater" (>) than it.
> >
> > > which is my current version of php and emerge said
> > > [ebuild NS ] dev-lang/php-5.1.6-r6 USE="berkdb cli crypt gdbm
> > > [...]
> >
> > interesting. Yes, that "NS" is for a New, Slotted version. I.e., PHP4
> > will still be on your system, so you might already stop worrying at
> > this point. In fact, I don't really know how to mask a version in a
> > different slot. I would have even expected my suggestion to do that
> > anyway. But this makes much more sense, because there should be a
> > seperate masking for each of the slots -- and it resembles the
> > behaviour from the profile's masks. So you might add another line to
> > your package.mask, following Boyd Stephen's suggestion to mask with
> > ">=":
> >
> > >=dev-lang/php-5.0.0
> >
> >
> >
> > -hwh
> > --
> > gentoo-user@gentoo.org mailing list
>
> --
> Your life is like a penny. You're going to lose it. The question is:
> How do
> you spend it?
>
> John Covici
> covici@ccs.covici.com
> --
> gentoo-user@gentoo.org mailing list
>
>
--
Ryan W Sims
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-11 18:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 14:50 [gentoo-user] how do I keep package from being updated? John Covici
2007-01-11 15:10 ` Hans-Werner Hilse
2007-01-11 16:32 ` John covici
2007-01-11 16:38 ` John covici
2007-01-11 16:56 ` Hans-Werner Hilse
2007-01-11 17:36 ` Bo Ørsted Andresen
2007-01-11 17:56 ` John covici
2007-01-11 18:09 ` Bo Ørsted Andresen
2007-01-11 18:09 ` Ryan Sims [this message]
2007-01-11 16:47 ` Neil Bothwick
2007-01-11 17:28 ` Bo Ørsted Andresen
2007-01-11 20:32 ` Neil Bothwick
2007-01-11 20:43 ` Bo Ørsted Andresen
2007-01-11 21:43 ` John covici
2007-01-11 21:51 ` kashani
2007-01-11 22:20 ` Bo Ørsted Andresen
2007-01-11 22:41 ` Neil Bothwick
2007-01-11 15:21 ` Boyd Stephen Smith Jr.
2007-01-11 17:30 ` Bo Ørsted Andresen
2007-01-11 17:48 ` Boyd Stephen Smith Jr.
2007-01-11 18:11 ` kashani
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=64e8d2f20701111009s3f3a4ab9ob57531ed343ac6e8@mail.gmail.com \
--to=rwsims@gmail.com \
--cc=gentoo-user@lists.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