From: Ryan Tandy <tarpman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: How to make emerge skirt a package built from tar.gz
Date: Tue, 13 Dec 2005 21:42:38 -0800 [thread overview]
Message-ID: <439FB0CE.9000705@gmail.com> (raw)
In-Reply-To: <87ek4gqm0a.fsf@newsguy.com>
reader@newsguy.com wrote:
>Ryan Tandy <tarpman@gmail.com> writes:
>
>
>
>>emerge --inject 'app-foo/bar-1.2.3'
>>
>>Sounds like that's what you're thinking of.
>>--
>>
>>
>
>That may be a way to do it. It isn't what I was thinking of though.
>I've never heard of this and man emerges has almost nothing to say
>about it. And `man inject' doesn't now about it at all.
>
>The man page makes a brief comment:
>
>[ebuild U-] x11-base/xfree-4.3.0 [4.2.99.902]
> The - represents lack of SLOT information about Xfree. This
> will occur when the previous version emerged was injected (see
> inject for more info) or very outdated (so old that SLOT did not
> exist). Either way, a newer version of Xfree is availabe for
> your updating delight.
>
>But fails to mention where one can `see inject'. That is the only
>occurance of `inject' in man emerge.
>
>I think is was something entered in /etc/portag/package.SOMETHING
>
>
>
I think emerge --inject is being deprecated, but I can't remember any
sort of alternative. What the command does is tell Portage to think a
package is installed, regardless of whether or not it is. I believe its
purpose is/was to allow developers to muck around with patches and
uber-unstable builds (e.g. CVS snapshots) without having to learn
ebuild-ing in order to satisfy dependencies on other packages.
Aha! A bit of effort solves everything!
tarpman@delta ~ $ emerge --inject
*** --inject has been deprecated.
*** If you manage a piece of software yourself, add it's name and
*** version (eg foo/bar-1.0) to /etc/portage/profile/package.provided.
*** If you want to prevent portage from upgrading a package, add it to
*** /etc/portage/package.mask prepending it with '>' (eg >foo/bar-1.0)
*** For more information on fine-grained portage control, please see
*** the portage man page.
emerge: root access required.
tarpman@delta ~ $
I have a feeling (Captain Obvious strikes again!) that
/etc/portage/profile/package.provided is what you're looking for...
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-14 5:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 5:06 [gentoo-user] How to make emerge skirt a package built from tar.gz reader
2005-12-14 4:18 ` Ryan Tandy
2005-12-14 5:35 ` [gentoo-user] " reader
2005-12-14 5:42 ` Ryan Tandy [this message]
2005-12-14 10:45 ` [gentoo-user] " Neil Bothwick
2005-12-15 3:20 ` [gentoo-user] " reader
2005-12-15 9:58 ` Neil Bothwick
2005-12-15 16:25 ` reader
-- strict thread matches above, loose matches on Subject: below --
2005-12-14 14:36 brettholcomb
2005-12-14 20:41 ` Robert Crawford
2005-12-15 0:34 ` Brett I. Holcomb
2005-12-15 0:54 ` reader
2005-12-15 0:22 ` Richard Fish
2005-12-15 7:33 ` Robert Crawford
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=439FB0CE.9000705@gmail.com \
--to=tarpman@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