Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 500458 - `ebuild ... manifest` should explain why no Manifest is created (when one isn't)
Summary: `ebuild ... manifest` should explain why no Manifest is created (when one isn't)
Status: CONFIRMED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Ebuild Support (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-06 02:09 UTC by SpanKY
Modified: 2014-02-06 02:09 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SpanKY gentoo-dev 2014-02-06 02:09:33 UTC
i've had more than one person ask me about this, so adding a single message explaining what ebuild is doing would help

basically, in a repo where you have thin-manifests turned on, a Manifest file is not created when SRC_URI is empty.  so if you go in to say a virtual dir and do:
$ ebuild editor-0.ebuild manifest
Appending /usr/local/src/chromiumos/src/third_party/portage-stable to PORTDIR_OVERLAY...
>>> Creating Manifest for /usr/local/src/chromiumos/src/third_party/portage-stable/virtual/editor

$ ls -l Manifest
ls: cannot access Manifest: No such file or directory

that's pretty confusing