AFAICT manifest generation is always package global, so there appears to be no difference between $ ebuild bla-2342-r3.ebuild manifest and $ ebuild bla-2342-r4.ebuild manifest instead of having to type $ ebuild bla-2342-r3.ebuild manifest I'd like to be able to regenerate the manifest for a package by simply typing $ ebuild manifest I use Portage 2.1.2.2. thanks kind regards Thilo
How is it supposed to know which package to operate on? Are you so lazy that you can't tab complete the ebuild name? :P
(In reply to comment #1) > How is it supposed to know which package to operate on? Are you so lazy that > you can't tab complete the ebuild name? :P > The current directory?
agaffney: i should have added something like $ ebuild manifest expands to $ebuild . manifest which is exactly what betelgeuse is suggesting and. i am not sure, that this is actually possible... and yes - i am THAT lazy... ;)
Perhaps it would be more appropriate to make this a new target for repoman. We already have a "fix" target which will do the manifest, but it also does other qa stuff. We can add a "manifest" target that just does the manifest.
Created attachment 119669 [details, diff] add a "manifest" target to repoman This is in svn r6554.
This has been released in 2.1.2.8.
thanks!