* [gentoo-user] Odd portage behaviour with binary packages
@ 2006-10-17 9:44 Stephane Pointu
2006-10-17 10:34 ` Alan McKinnon
2006-10-17 10:49 ` Bo Ørsted Andresen
0 siblings, 2 replies; 6+ messages in thread
From: Stephane Pointu @ 2006-10-17 9:44 UTC (permalink / raw
To: gentoo-user
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all, I have a question about portage behaviour:
I have a package built in a certain version in /usr/portage/package but
this version is not in portage tree (no ebuild for it). If I do a
"emerge -kuav world" it takes this package but if I do a "emerge -uav
world" it does not. Is this a normal behaviour? Shouldn't portage first
check if there is an ebuild for it before installing the package?
Regards,
Stephane
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFNKXrWWLMt96bzSoRAm6DAJwKuXH8WXZGc8p1gZYcuRq+Nd3LUwCePxRJ
8WgIpWPIClhC7IgNqg+yKAs=
=eRIS
-----END PGP SIGNATURE-----
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] Odd portage behaviour with binary packages
2006-10-17 9:44 [gentoo-user] Odd portage behaviour with binary packages Stephane Pointu
@ 2006-10-17 10:34 ` Alan McKinnon
2006-10-17 12:17 ` Stephane Pointu
2006-10-17 10:49 ` Bo Ørsted Andresen
1 sibling, 1 reply; 6+ messages in thread
From: Alan McKinnon @ 2006-10-17 10:34 UTC (permalink / raw
To: gentoo-user
On Tuesday 17 October 2006 11:44, Stephane Pointu wrote:
> Hi all, I have a question about portage behaviour:
>
> I have a package built in a certain version in /usr/portage/package
> but this version is not in portage tree (no ebuild for it). If I do a
> "emerge -kuav world" it takes this package but if I do a "emerge -uav
> world" it does not. Is this a normal behaviour? Shouldn't portage
> first check if there is an ebuild for it before installing the
> package?
No, it makes perfect sense. When you use the -k switch, portage is in a
position to find and use the prebuilt package, so it will.
When you don't use the -k switch, it won't use /usr/portage/packages per
the man page, so there's no sense in even attemtping to look for that
package - as there is no ebuild for that version, it cannot possibly
build it
Your last question doesn't make sense - how can portage check for an
ebuild that you earlier clearly said does not exist?
alan
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] Odd portage behaviour with binary packages
2006-10-17 10:34 ` Alan McKinnon
@ 2006-10-17 12:17 ` Stephane Pointu
0 siblings, 0 replies; 6+ messages in thread
From: Stephane Pointu @ 2006-10-17 12:17 UTC (permalink / raw
To: gentoo-user
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
You didn't get my point. The global idea was that I thought that Portage
first checks ebuilds before installing any package, and as there was no
ebuild, the package shouldn't get installed. I did not know that there
was the ebuild in the package itself.
Stephane
Alan McKinnon wrote:
> On Tuesday 17 October 2006 11:44, Stephane Pointu wrote:
>> Hi all, I have a question about portage behaviour:
>>
>> I have a package built in a certain version in /usr/portage/package
>> but this version is not in portage tree (no ebuild for it). If I do a
>> "emerge -kuav world" it takes this package but if I do a "emerge -uav
>> world" it does not. Is this a normal behaviour? Shouldn't portage
>> first check if there is an ebuild for it before installing the
>> package?
>
> No, it makes perfect sense. When you use the -k switch, portage is in a
> position to find and use the prebuilt package, so it will.
>
> When you don't use the -k switch, it won't use /usr/portage/packages per
> the man page, so there's no sense in even attemtping to look for that
> package - as there is no ebuild for that version, it cannot possibly
> build it
>
> Your last question doesn't make sense - how can portage check for an
> ebuild that you earlier clearly said does not exist?
>
> alan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFNMnbWWLMt96bzSoRAjLXAKCMyIind950O8x+r/zqJ3oj2cqXdgCgnenu
ImG22gm7zhrCSTrk8BjVvos=
=zu0Y
-----END PGP SIGNATURE-----
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] Odd portage behaviour with binary packages
2006-10-17 9:44 [gentoo-user] Odd portage behaviour with binary packages Stephane Pointu
2006-10-17 10:34 ` Alan McKinnon
@ 2006-10-17 10:49 ` Bo Ørsted Andresen
2006-10-17 12:12 ` Stephane Pointu
1 sibling, 1 reply; 6+ messages in thread
From: Bo Ørsted Andresen @ 2006-10-17 10:49 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Tuesday 17 October 2006 11:44, Stephane Pointu wrote:
> Hi all, I have a question about portage behaviour:
>
> I have a package built in a certain version in /usr/portage/package but
> this version is not in portage tree (no ebuild for it). If I do a
> "emerge -kuav world" it takes this package but if I do a "emerge -uav
> world" it does not. Is this a normal behaviour? Shouldn't portage first
> check if there is an ebuild for it before installing the package?
The binary tbz2 package does contain the ebuild and any other information
necessary for installing the binary package. qtbz2 from
app-portage/portage-utils can be used to extract the metadata from a tbz2
file..
--
Bo Andresen
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] Odd portage behaviour with binary packages
2006-10-17 10:49 ` Bo Ørsted Andresen
@ 2006-10-17 12:12 ` Stephane Pointu
2006-10-17 12:26 ` Bo Ørsted Andresen
0 siblings, 1 reply; 6+ messages in thread
From: Stephane Pointu @ 2006-10-17 12:12 UTC (permalink / raw
To: gentoo-user
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
OK. Actually I didn't know that the ebuild was in the package. However
when I tried to uncompress the archive to see what's in it, I had the
following error:
bzip2: (stdin): trailing garbage after EOF ignored
I have the same error on all packages in /usr/portage/packages
In the piece of data I managed to untar, I don't find any ebuild. I
guess it's in the "trailing garbage". Is there a way to extract it?
Regards,
Stephane
Bo Ørsted Andresen wrote:
> The binary tbz2 package does contain the ebuild and any other information
> necessary for installing the binary package. qtbz2 from
> app-portage/portage-utils can be used to extract the metadata from a tbz2
> file..
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFNMiYWWLMt96bzSoRAkuYAJ4uBEylERT5i10iUR+MENI1rr3xlQCeP+jA
hc0CkYTXzzCo0SkKt70ujSc=
=nDoY
-----END PGP SIGNATURE-----
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-10-17 12:35 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-17 9:44 [gentoo-user] Odd portage behaviour with binary packages Stephane Pointu
2006-10-17 10:34 ` Alan McKinnon
2006-10-17 12:17 ` Stephane Pointu
2006-10-17 10:49 ` Bo Ørsted Andresen
2006-10-17 12:12 ` Stephane Pointu
2006-10-17 12:26 ` Bo Ørsted Andresen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox