Bug 176539 – ebuild manifest shorthand

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Thilo Bangert (RETIRED) (RETIRED) 2007-04-30 08:45:14 UTC]

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

[Comment 1 Andrew Gaffney (RETIRED) 2007-04-30 12:25:40 UTC]

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

[Comment 2 Petteri Räty (RETIRED) 2007-04-30 14:08:47 UTC]

(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?

[Comment 3 Thilo Bangert (RETIRED) (RETIRED) 2007-04-30 21:28:49 UTC]

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... ;)

[Comment 4 Zac Medico 2007-05-18 17:50:53 UTC]

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.

[Comment 5 Zac Medico 2007-05-19 04:38:05 UTC]

Created attachment 119669 [details, diff]
add a "manifest" target to repoman

This is in svn r6554.

[Comment 6 Zac Medico 2007-05-25 09:06:37 UTC]

This has been released in 2.1.2.8.

[Comment 7 Thilo Bangert (RETIRED) (RETIRED) 2007-05-25 18:24:35 UTC]

thanks!