Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 875359 - ebuild manifest: improve behavior
Summary: ebuild manifest: improve behavior
Status: CONFIRMED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-05 09:40 UTC by Agostino Sarubbo
Modified: 2022-10-20 02:18 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2022-10-05 09:40:19 UTC 
The correct syntax for ebuild manifest is:

ebuild foo-1.ebuild manifest

However if I have other foo-*.ebuild in the same directory, everything related to foo-*.ebuild is generated too in the Manifest.

So why not simplify the behavior like doing only: "ebuild manifest" ?
Comment 1 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-10-05 09:53:30 UTC 
>However if I have other foo-*.ebuild in the same directory, everything related to foo-*.ebuild is generated too in the Manifest.

Could you explain what you mean here? Maybe with a set of commands and output.
Comment 2 Agostino Sarubbo gentoo-dev 2022-10-05 10:07:45 UTC 
(In reply to Sam James from comment #1)
> Could you explain what you mean here? Maybe with a set of commands and
> output.

Sure:

I'm in sys-devel/bison directory so:
~ $ ls -la *.ebuild
-rw-r--r-- 1 ago ago 2434 ago  2 08:44 bison-3.7.6.ebuild
-rw-r--r-- 1 ago ago 2683 ago  2 08:44 bison-3.8.2.ebuild

~ $ mv Manifest Manifest.old
~ $ ebuild bison-3.7.6.ebuild manifest
~ $ diff -ru Manifest.old Manifest
~ $ cat Manifest
DIST bison-3.7.6-patches-01.tar.xz 10600 BLAKE2B c7907a327c2bbb82a2e575a864e71400f91cd4349a84f95b187ecaadefc1bfd595a91bce6c8c47e42423cace9cf78a4041fde3fdc489a4824aa3c10ca73be7cb SHA512 8f2ddee79b9678b9fd9a7a34f26d44f7c4472d0fc55c9fef8b418d27949b6a27309b7aa5ac3f4a5ad27c90ad7d92d824ffe767c77b0ed81de6b2897c91cd7560
DIST bison-3.7.6.tar.xz 2627180 BLAKE2B 2f1015b517e46ff0870378b4d0dd489c8c737f31b2b69146bd7fbbae1e3adcdff0e4837cfdf1d238e8660ecc2b310ce87ec8940ed4989278b3df6cbb2d464e54 SHA512 6c1c9b825fbd2c94b8903f03a7e68e6832599f7bbd8d3c49864537c11b038c45a15de02fd36128d662af314334c83515bbc132df84e9acc6c651e98649c65bad
DIST bison-3.8.2.tar.xz 2817324 BLAKE2B e211b61494c911f55b72a8b70b5a48cdf4000ce9e675a1f1f52735bb8f57d93a3f8075341451263af9c9c531004907ae2b62b1873e7e4664c2cd26fa3b12271c SHA512 d4d23af6671406e97257892f90651b67f2ab95219831372be032190b7156c10a3435d457857e677445df8b2327aacccc15344acbbc3808a6f332a93cce23b444
DIST bison-3.8.2.tar.xz.sig 195 BLAKE2B b9bd21adb5115d3d3174c94223fbc9cd33afa0e9c1805008e49f77ff154fc2b656d8a9e9503dc5290658ae2948a2ca7c0dbc812f62aec268d8f8bfafb6349096 SHA512 8bb7743ca326e81a6c091b1413e3c09bd43c7eabbb80bac0638ccd52bdf7e3395cce300a86acd95f4637a9ec8a1b0e9a4d3d25d95ab0a8f03e57fd82eb87a7ac


So I mean that run "ebuild bison-3.7.6.ebuild manifest" or "ebuild bison-3.8.2.ebuild manifest" produces the same Manifest, so why not avoid to specify the ebuild file as argument since it is not specific to that file?
Comment 3 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-10-20 02:18:04 UTC 
Is this a duplicate of bug 707334?