| 1 |
On Tue, Jul 7, 2009 at 1:40 AM, Amit Dor-Shifer<amitds@××××××.com> wrote: |
| 2 |
> amit0 ~ # ls -la /var/db/pkg/var |
| 3 |
> ls: cannot access /var/db/pkg/var: No such file or directory |
| 4 |
> amit0 ~ # ls -la /var/db/pkg/tmp |
| 5 |
> ls: cannot access /var/db/pkg/tmp: No such file or directory |
| 6 |
> amit0 ~ # portageq match /var/db/pkg portage |
| 7 |
|
| 8 |
Just FYI, you are probably misinterpreted what <root> means here; |
| 9 |
which is why you are confused later on. |
| 10 |
|
| 11 |
> amit0 ~ # find /var/db/pkg/var /var/db/pkg/tmp |
| 12 |
> /var/db/pkg/var |
| 13 |
> /var/db/pkg/var/tmp |
| 14 |
> /var/db/pkg/var/lib |
| 15 |
> /var/db/pkg/var/lib/portage |
| 16 |
> /var/db/pkg/var/cache |
| 17 |
> /var/db/pkg/var/cache/edb |
| 18 |
> /var/db/pkg/tmp |
| 19 |
|
| 20 |
Of course it wouldn't; those directories are not at all designed to be |
| 21 |
temporary. |
| 22 |
|
| 23 |
/var/cache/edb is a metadata cache. /var/lib/portage holds cached |
| 24 |
config entries, --resume stuff, world files, and the preserved libs |
| 25 |
registry. Deleting those every time portageq runs would be crazy. |
| 26 |
|
| 27 |
> amit0 ~ # emerge -Op portage |
| 28 |
> !!! Invalid db entry: /var/db/pkg/var/tmp |
| 29 |
> !!! Invalid db entry: /var/db/pkg/var/lib |
| 30 |
> !!! Invalid db entry: /var/db/pkg/var/cache |
| 31 |
> |
| 32 |
> These are the packages that would be merged, in order: |
| 33 |
> |
| 34 |
> !!! Invalid db entry: /var/db/pkg/var/tmp |
| 35 |
> !!! Invalid db entry: /var/db/pkg/var/lib |
| 36 |
> !!! Invalid db entry: /var/db/pkg/var/cache |
| 37 |
> [ebuild U ] sys-apps/portage-2.1.6.11 [2.1.6.7] |
| 38 |
> !!! Invalid db entry: /var/db/pkg/var/tmp |
| 39 |
> !!! Invalid db entry: /var/db/pkg/var/lib |
| 40 |
> !!! Invalid db entry: /var/db/pkg/var/cache |
| 41 |
|
| 42 |
match <root> <atom> |
| 43 |
Returns a \n separated list of category/package-version. |
| 44 |
When given an empty string, all installed packages will |
| 45 |
be listed. |
| 46 |
|
| 47 |
<root> is: |
| 48 |
ROOT = [path] |
| 49 |
Use ROOT to specify the target root filesystem to be |
| 50 |
used for merging packages or ebuilds. This variable can be set via |
| 51 |
the --root option or in make.conf(5) (the command line |
| 52 |
overrides other settings). |
| 53 |
Defaults to /. |
| 54 |
|
| 55 |
You probably want portageq has_version / 'sys-apps/portage' ? |
| 56 |
|
| 57 |
maybe Zac can make has_version take atoms? |
| 58 |
|
| 59 |
> |
| 60 |
> |
| 61 |
> |
Archives