| View previous topic :: View next topic |
| Author |
Message |
CaptainBlood
Advocate
Joined: 24 Jan 2010
Posts: 3938
|
 Posted: Mon Oct 28, 2024 5:10 pm Post subject: binpkg-multi-instance emerge vs quickpkg internal issue |
 |
|
Depending which tool is used to create a gentoo arbitrary binary package,
internal structure of the generated package differs here.
Testing here: | Code: | emerge --buildpkgonly virtual/man
These are the packages that would be built, in reverse order:
Calculating dependencies ..... done!
Dependency resolution took 13.01 s (backtrack: 0/20).
[ebuild R ] virtual/man-0-r4
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) virtual/man-0-r4::gentoo
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/virtual/man-0-r4/work
>>> Preparing source in /var/tmp/portage/virtual/man-0-r4/work ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/virtual/man-0-r4/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/virtual/man-0-r4/work ...
>>> Source compiled.
>>> Test phase [not enabled]: virtual/man-0-r4
>>> Install virtual/man-0-r4 into /var/tmp/portage/virtual/man-0-r4/image
>>> Completed installing virtual/man-0-r4 into /var/tmp/portage/virtual/man-0-r4/image
* Final size of build directory: 0 KiB
* Final size of installed tree: 0 KiB
>>> Done.
--------------------------------------
ls -l /var/cache/binpkgs/virtual/man/
total 20
-rw-r--r-- 1 root root 20480 oct. 28 19:45 man-0-r4-1.gpkg.tar
-----------------------------------------------------------
tar -tvf /var/cache/binpkgs/virtual/man/man-0-r4-1.gpkg.tar
-rw-r--r-- 0/0 0 2024-10-28 19:45 man-0-r4-1/gpkg-1
-rw-r--r-- 0/0 8864 2024-10-28 19:45 man-0-r4-1/metadata.tar.xz
-rw-r--r-- 0/0 176 2024-10-28 19:45 man-0-r4-1/image.tar.xz
-rw-r--r-- 0/0 881 2024-10-28 19:45 man-0-r4-1/Manifest |
Plz note the containing directory in the tar 'man-0-r4-1' matches the file name.
| Code: | quickpkg --include-config n --umask 0072 virtual/man
* Building package for virtual/man-0-r4 ... [ ok ]
* Packages now in '/var/cache/binpkgs':
* virtual/man-0-r4: 20.0K
-------------------------------------
ls -l /var/cache/binpkgs/virtual/man/
total 40
-rw-r--r-- 1 root root 20480 oct. 28 19:45 man-0-r4-1.gpkg.tar
-rw-r--r-- 1 root root 20480 oct. 28 19:46 man-0-r4-2.gpkg.tar
-----------------------------------------------------------
tar -tvf /var/cache/binpkgs/virtual/man/man-0-r4-2.gpkg.tar
-rw-r--r-- 0/0 0 2024-10-28 19:46 man-0-r4/gpkg-1
-rw-r--r-- 0/0 8620 2024-10-28 19:46 man-0-r4/metadata.tar.xz
-rw-r--r-- 0/0 156 2024-10-28 19:46 man-0-r4/image.tar.xz
-rw-r--r-- 0/0 881 2024-10-28 19:46 man-0-r4/Manifest |
Plz note the containing directory name in the tar 'man-0-r4' which DOES'NT matches the file name, i.e. 'man-0-r4-2'.
I'd expect both commands results to be more consistent 
What may be missing here?
Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "
Last edited by CaptainBlood on Wed Nov 27, 2024 11:25 pm; edited 6 times in total |
|
| Back to top |
|
 |
bstaletic
Guru
Joined: 05 Apr 2014
Posts: 381
|
| Posted: Mon Oct 28, 2024 5:32 pm Post subject: |
|
|
It's not about different tools. It's about the specification of GPKG format.
I had the same question. |
|
| Back to top |
|
|
CaptainBlood
Advocate
Joined: 24 Jan 2010
Posts: 3938
|
| Posted: Mon Oct 28, 2024 6:19 pm Post subject: |
|
|
Indeed
FEATURES=-binpkg-multi-instance brings:
Consistency between binary package names between tools.
Consistency between the binary package name and its content, whatever tool is used.
Let's call it full consistency.
I think this is a little # issue:
FEATURES=binpkg-multi-instance brings
Consistency between binary package names between tools.
Consistency between the binary package name and its content, when using emerge.
Inconsistency between the binary package name and its content, when using quickpkg.
Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
| Back to top |
|
|
pingtoo
Veteran
Joined: 10 Sep 2021
Posts: 1290
Location: Richmond Hill, Canada
|
| Posted: Mon Oct 28, 2024 7:04 pm Post subject: |
|
|
Does this mean the result binary package can (or cannot) be use interchangeable?
i.e. can quickpkg created package be use by emerge -K and vice versa? |
|
| Back to top |
|
|
eschwartz
Developer
Joined: 29 Oct 2023
Posts: 240
|
| Posted: Tue Oct 29, 2024 1:31 am Post subject: |
|
|
| The binary package can be used just fine. I am not sure the containing directory actually matters, here. |
|
| Back to top |
|
|
CaptainBlood
Advocate
Joined: 24 Jan 2010
Posts: 3938
|
| Posted: Tue Oct 29, 2024 8:02 am Post subject: |
|
|
| eschwartz wrote: | | The binary package can be used just fine. I am not sure the containing directory actually matters, here. |
Indeed, emerge -K works fine in both cases. 
Plz note quickpkg belongs to sys-apps/portage.
So the same package provide 2 ways to generate the same kind of an object with internal differences.
As soon as you want to inspect a binary package content, there is an alternative depending how the package has been generated.
Things could be simpler, more consistent.
Time for me to find how to patch quickpkg accordingly... 
Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
| Back to top |
|
|
CaptainBlood
Advocate
Joined: 24 Jan 2010
Posts: 3938
|
| Posted: Tue Oct 29, 2024 6:58 pm Post subject: |
|
|
It so happened I put the blame on quickpkg because generated internal root directory doesn't mach binary package file name, which endswith -{multi-indice}.gpkg.tar.
Considering the other way round seems also valid: generated internal root directory should only strictly refers to pf. From this pov emerge would be to blame.
Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
| Back to top |
|
|
CaptainBlood
Advocate
Joined: 24 Jan 2010
Posts: 3938
|
| Posted: Wed Nov 27, 2024 11:22 pm Post subject: |
|
|
Report
Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
| Back to top |
|
|
|
Other Things Gentoo
