Hi. I just did emerge --pretend --update --deep world, but there is a
package which I don't want to have emerge update automatically -- how
do I accomplish this?
Thanks.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
Hi,
On Thu, 11 Jan 2007 09:50:31 -0500 John Covici [EMAIL PROTECTED]
wrote:
Hi. I just did emerge --pretend --update --deep world, but there is a
package which I don't want to have emerge update automatically -- how
do I accomplish this?
You can mask it in /etc/portage/package.mask, for the
On Thursday 11 January 2007 08:50, John Covici [EMAIL PROTECTED]
wrote about '[gentoo-user] how do I keep package from being updated?':
Hi. I just did emerge --pretend --update --deep world, but there is a
package which I don't want to have emerge update automatically -- how
do I accomplish
OK, thanks I will try that and see what it does.
on Thursday 01/11/2007 Hans-Werner Hilse([EMAIL PROTECTED]) wrote
Hi,
On Thu, 11 Jan 2007 09:50:31 -0500 John Covici [EMAIL PROTECTED]
wrote:
Hi. I just did emerge --pretend --update --deep world, but there is a
package which I
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
which is my current version of php and emerge said
[ebuild NS ]
On Thu, 11 Jan 2007 16:10:29 +0100, Hans-Werner Hilse wrote:
You can mask it in /etc/portage/package.mask, for the syntax have a
look at man 5 portage. For your case, it's basically a line like
pkg-category/package-0.0.1
assuming you want to keep 0.0.1.
It would be better to use
Hi,
On Thu, 11 Jan 2007 11:38:38 -0500
John covici [EMAIL PROTECTED] 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
On Thursday 11 January 2007 17:47, Neil Bothwick wrote:
It would be better to use ~pkg-category/package-0.0.1. this allows
patch level updates, such as 0.0.1-r1 while not permitting an update to a
higher upstream version.
That isn't a valid atom and it plain doesn't work. Even if it did it
On Thursday 11 January 2007 16:21, Boyd Stephen Smith Jr. wrote:
add =cate-gory/package-1.6* to your package.mask
That too isn't a valid atom. Lose the '*'. It's only valid with '=' not '='
or '~'... Valid atoms are described in `man 5 ebuild`.
--
Bo Andresen
pgp9EzkNnmr9O.pgp
Description:
On Thursday 11 January 2007 17:56, Hans-Werner Hilse wrote:
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
On Thursday 11 January 2007 11:30, Bo Ørsted Andresen [EMAIL PROTECTED]
wrote about 'Re: [gentoo-user] how do I keep package from being updated?':
On Thursday 11 January 2007 16:21, Boyd Stephen Smith Jr. wrote:
add =cate-gory/package-1.6* to your package.mask
That too isn't a valid atom
If I have two versions on the systems, how would apache and the cli
pick what version they are going to use?
on Thursday 01/11/2007 Hans-Werner Hilse([EMAIL PROTECTED]) wrote
Hi,
On Thu, 11 Jan 2007 11:38:38 -0500
John covici [EMAIL PROTECTED] wrote:
OK, I did put my php version in
On 1/11/07, John covici [EMAIL PROTECTED] 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
On Thursday 11 January 2007 18:56, John covici wrote:
If I have two versions on the systems, how would apache and the cli
pick what version they are going to use?
Apparently there's a php-select tool [1]. And I think apache has separate init
scripts and use flags for each slot. You should have
John Covici wrote:
Hi. I just did emerge --pretend --update --deep world, but there is a
package which I don't want to have emerge update automatically -- how
do I accomplish this?
Thanks.
Assuming this is going back to the PHP thing, this will allow you to
update to future versions of 4.x
On Thu, 11 Jan 2007 18:28:51 +0100, Bo Ørsted Andresen wrote:
It would be better to use ~pkg-category/package-0.0.1. this allows
patch level updates, such as 0.0.1-r1 while not permitting an update
to a higher upstream version.
That isn't a valid atom and it plain doesn't work. Even if
On Thursday 11 January 2007 21:32, Neil Bothwick wrote:
It would be better to use ~pkg-category/package-0.0.1. this allows
patch level updates, such as 0.0.1-r1 while not permitting an update
to a higher upstream version.
That isn't a valid atom and it plain doesn't work. Even if it
Also, what did work was dev-lang/php-5 I wish there was a way to see
what it was ignoring, etc.
on Thursday 01/11/2007 Bo Ørsted Andresen([EMAIL PROTECTED]) wrote
On Thursday 11 January 2007 21:32, Neil Bothwick wrote:
It would be better to use ~pkg-category/package-0.0.1. this allows
John covici wrote:
Also, what did work was dev-lang/php-5 I wish there was a way to see
what it was ignoring, etc.
emerge eix
eix -pv php
kashani
--
gentoo-user@gentoo.org mailing list
On Thursday 11 January 2007 22:43, John covici wrote:
Also, what did work was dev-lang/php-5 I wish there was a way to see
what it was ignoring, etc.
An invalid atom like e.g.: =dev-lang/php-4* will make portage 2.1.2 spit
out a warning about it being an invalid atom. I do consider the fact
On Thu, 11 Jan 2007 21:43:34 +0100, Bo Ørsted Andresen wrote:
I tested it before posting and it did work. It didn't mask -r*,
allowing a upgrade.
It doesn't work at all. Nothing gets masked. It's simply ignored:
You're right, I didn't test very effectively. I should have just checked
21 matches
Mail list logo