Jason Stubbs wrote:
> A. Khattri wrote:
>
>> On Thu, 1 Dec 2005, Robert Larson wrote:
>>
>>> If I understand you correctly, then this may help:
>>> # obtain a list of installed packages
>>> emerge -vep world | grep ^'\[ebuild ' | while read a; do
>>> # extract the package name
>>> pkg=$(echo $a | cut -d']' -f2 | awk '{print $1}')
>>> # build a binary of the package
>>> quickpkg "/var/db/pkg/${pkg}"
>>> done
>>
>>
>> I came up with this (yes, granted it is tied to the file-system layout
>> but
>> its damn fast!):
>>
>> find /var/db/pkg -mindepth 2 -maxdepth 2 -print -exec quickpkg {} \;
>
>
> I was thinking about extending quickpkg to support syntax like:
> quickpkg [--deep [--build-deps] ] [--overwrite] <atom>|<target>
>
> <atom> is one or more regular atoms. <target> is any supported target
> (currently "world" or "system"). --deep would recursively make packages
> of runtime dependencies. --build-deps would include build time
> dependencies (which of course aren't actually needed). --overwrite
> would cause packages to be created even if they already exist in PKGDIR.
>
> Can I take this thread as an expression of interest in the above?
> Anything missing or would be better done differently?
Yes!
And, but not sure how, adding something like --update and --update-only will
save some cpu cycles.
Actually, may be you are right. --overwrite might be better, but I was thinking
about emerge syntax.
Kalin.
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
--
[email protected] mailing list
