Re: [gentoo-user] Re: How to make emerge skirt a package built from tar.gz

Re: [gentoo-user] Re: How to make emerge skirt a package built from tar.gz

[brettholcomb]

Isn't /etc/package/provides the proper way to do this as inject is deprecated?


> 
> From: reader@newsguy.com
> Date: 2005/12/14 Wed AM 12:35:17 EST
> To: gentoo-user@lists.gentoo.org
> Subject: [gentoo-user]  Re: How to make emerge skirt a package built from tar.gz
> 
> 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:


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: How to make emerge skirt a package built from tar.gz

[Robert Crawford]

On Wednesday 14 December 2005 09:36, brettholcomb@bellsouth.net wrote:
> Isn't /etc/package/provides the proper way to do this as inject is
> deprecated?

It's: 
/etc/portage/profile/package.provided


>
> > From: reader@newsguy.com
> > Date: 2005/12/14 Wed AM 12:35:17 EST
> > To: gentoo-user@lists.gentoo.org
> > Subject: [gentoo-user]  Re: How to make emerge skirt a package built from
> > tar.gz
> >
> > 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:
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: How to make emerge skirt a package built from tar.gz

[Brett I. Holcomb]

Arrgh, trying to do it from memory!  Thanks for the correction.

On Wednesday 14 December 2005 15:41, Robert Crawford wrote:
> On Wednesday 14 December 2005 09:36, brettholcomb@bellsouth.net wrote:
> > Isn't /etc/package/provides the proper way to do this as inject is
> > deprecated?
>
> It's:
> /etc/portage/profile/package.provided
>
> > > From: reader@newsguy.com

-- 

Brett I. Holcomb
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: How to make emerge skirt a package built from tar.gz

[reader]

Robert Crawford <flacycads@cox.net> writes:

> On Wednesday 14 December 2005 09:36, brettholcomb@bellsouth.net wrote:
>> Isn't /etc/package/provides the proper way to do this as inject is
>> deprecated?
>
> It's: 
> /etc/portage/profile/package.provided

Is it really /etc/portage/profile though?  All my other `package'
files are at /etc/portage

 ls /etc/portage
  package.keywords  package.keywords~  package.use  package.use~ 

I saw the output from emerge posted here and it does say:
   /etc/portage/profile/package.provided

I just wondered if that is deprecated in favor of
/etc/portage/package.provided since all the other package adjustment
files are there and seem to work from there as expected.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: How to make emerge skirt a package built from tar.gz

[Richard Fish]

On 12/14/05, reader@newsguy.com <reader@newsguy.com> wrote:
> Robert Crawford <flacycads@cox.net> writes:
>
> > On Wednesday 14 December 2005 09:36, brettholcomb@bellsouth.net wrote:
> >> Isn't /etc/package/provides the proper way to do this as inject is
> >> deprecated?
> >
> > It's:
> > /etc/portage/profile/package.provided
>
> Is it really /etc/portage/profile though?  All my other `package'
> files are at /etc/portage


>From "man portage":

       /etc/portage/profile/
              site-specific overrides of /etc/make.profile/

The read the file descriptions under /etc/make.profile/

> I just wondered if that is deprecated in favor of
> /etc/portage/package.provided since all the other package adjustment
> files are there and seem to work from there as expected.

Again, man portage.  /etc/portage/package.provided will be ignored.

-Richard


>
> --
> gentoo-user@gentoo.org mailing list
>
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: How to make emerge skirt a package built from tar.gz

[Robert Crawford]

On Wednesday 14 December 2005 19:54, reader@newsguy.com wrote:
> Robert Crawford <flacycads@cox.net> writes:
> > On Wednesday 14 December 2005 09:36, brettholcomb@bellsouth.net wrote:
> >> Isn't /etc/package/provides the proper way to do this as inject is
> >> deprecated?
> >
> > It's:
> > /etc/portage/profile/package.provided
>
> Is it really /etc/portage/profile though?  All my other `package'
> files are at /etc/portage
>
>  ls /etc/portage
>   package.keywords  package.keywords~  package.use  package.use~
>
> I saw the output from emerge posted here and it does say:
>    /etc/portage/profile/package.provided
>
> I just wondered if that is deprecated in favor of
> /etc/portage/package.provided since all the other package adjustment
> files are there and seem to work from there as expected.


 /etc/portage/profile/package.provided always works for me. However, I don't 
know if its location is being  changed to  /etc/portage/package.provided, 
where all the other files are placed.  I did wonder why package.provided 
needed a "profile" directory, but have never seen the reason mentioned 
anywhere.

R.C.
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] How to make emerge skirt a package built from tar.gz

[reader]

I'm about to run an update world following a sync and I noitce that
cvs is one of the packages involved.  I couldn't remember how to make
emerge use a specific ./configure flag.  Not sure I ever really
understood that whole business anyway, although Holly and others have
attempted to explain it to me.

I wanted to use `./configure --enable-rootcommit' (or similar) since
this is a single user machine.  

It didn't seem worth learning to build my own ebuild so I built it
from tar.gz and installed on /usr/local.  Then unmerged the existing
cvs installation.  Now as I recall there is some syntax that needs to go
into one of the possible files under /etc/portage to cause future
emerges like the upcoming update to ignore cvs, but I've forgotten
it. 

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] How to make emerge skirt a package built from tar.gz

[Ryan Tandy]

emerge --inject 'app-foo/bar-1.2.3'

Sounds like that's what you're thinking of.
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: How to make emerge skirt a package built from tar.gz

[reader]

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

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: How to make emerge skirt a package built from tar.gz

[Ryan Tandy]

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

Re: [gentoo-user] How to make emerge skirt a package built from tar.gz

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]

On Tue, 13 Dec 2005 23:06:45 -0600, reader@newsguy.com wrote:


> I'm about to run an update world following a sync and I noitce that
> cvs is one of the packages involved.  I couldn't remember how to make
> emerge use a specific ./configure flag.  Not sure I ever really
> understood that whole business anyway, although Holly and others have
> attempted to explain it to me.
> 
> I wanted to use `./configure --enable-rootcommit' (or similar) since
> this is a single user machine.  

EXTRA_ECONF="--enable-rootcommit" emerge cvs

usually works, although not all ebuilds respect $EXTRA_ECONF.

> It didn't seem worth learning to build my own ebuild so I built it
> from tar.gz and installed on /usr/local.  Then unmerged the existing
> cvs installation.  Now as I recall there is some syntax that needs to go
> into one of the possible files under /etc/portage to cause future
> emerges like the upcoming update to ignore cvs, but I've forgotten
> it. 

The file you need is /etc/portage/profile/package.provided, it is
documented in the portage manpage.

echo "dev-util/cvs-x.y.z" >>/etc/portage/profile/package.provided

should do it, where x.y.z is the version you have installed.


-- 
Neil Bothwick

Unsolicited advice is the junk mail of life

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: How to make emerge skirt a package built from tar.gz

[reader]

Neil Bothwick <neil@digimed.co.uk> writes:

[...]


>> I wanted to use `./configure --enable-rootcommit' (or similar) since
>> this is a single user machine.  
>
> EXTRA_ECONF="--enable-rootcommit" emerge cvs
>
> usually works, although not all ebuilds respect $EXTRA_ECONF.

Can you make an educated guess about that?  I mean is it a pretty high
percentage that allow that env flag?

>> It didn't seem worth learning to build my own ebuild so I built it
>> from tar.gz and installed on /usr/local.  Then unmerged the existing
>> cvs installation.  Now as I recall there is some syntax that needs to go
>> into one of the possible files under /etc/portage to cause future
>> emerges like the upcoming update to ignore cvs, but I've forgotten
>> it. 
>
> The file you need is /etc/portage/profile/package.provided, it is
> documented in the portage manpage.
>
> echo "dev-util/cvs-x.y.z" >>/etc/portage/profile/package.provided
>
> should do it, where x.y.z is the version you have installed.

That is good info even though it is apparently readily available ..
I've left it here just in case it helps one other reader notice the
usefullness of that

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: How to make emerge skirt a package built from tar.gz

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 628 bytes --]

On Wed, 14 Dec 2005 21:20:59 -0600, reader@newsguy.com wrote:

> > EXTRA_ECONF="--enable-rootcommit" emerge cvs
> >
> > usually works, although not all ebuilds respect $EXTRA_ECONF.
> 
> Can you make an educated guess about that?  I mean is it a pretty high
> percentage that allow that env flag?

No, and it wouldn't matter. Even if 99.9% of ebuilds respected it, yours
could be in the other 0.1%. It should be fairly high though. Just run the
command, Ctrl-C when the ./configure stage has completed and look in
config.log in the work directory.


-- 
Neil Bothwick

Windows: just another pane in the glass

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: How to make emerge skirt a package built from tar.gz

[reader]

Neil Bothwick <neil@digimed.co.uk> writes:

> No, and it wouldn't matter. Even if 99.9% of ebuilds respected it, yours
> could be in the other 0.1%. It should be fairly high though. Just run the
> command, Ctrl-C when the ./configure stage has completed and look in
> config.log in the work directory.

Good plan and yes it did work in this case... thanks

-- 
gentoo-user@gentoo.org mailing list