>>>>> Enrico Zini <[email protected]> writes:
> this is almost all implemented in version 1.6.2: if the index needs
> to be rebuilt and debtags is run as non-root, then the index will be
> rebuilt in ~/.debtags.
> The index will also be rebuilt in ~/.debtags if the user provides
> extra tag and vocabulary files in ~/.debtags.
I guess that this change was somehow reverted. Consider, e. g.:
$ debtags update
I do not have permission to write to /var/lib/debtags
fetcher command /usr/bin/debtags-fetch update failed. Context:
acquiring new data
$ dpkg -l debtags
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii debtags 1.10.1 amd64 Enables support for package tags
$
> What is still missing before closing this bug is to allow the user to
> specify a different sources.list and have the fetcher support
> fetching local tag sources.
My suggestion would be to use a couple of environment variables
(perhaps with corresponding command-line options), to specify
the directories to be used instead of /etc/debtags and
/var/lib/debtags, respectively.
I'd like to note that APT already supports both APT_CONFIG and
--config-file=, which allow most operations (i. e., with the
sole exception of the actual installation) to be performed by an
unprivileged user.
--
FSF associate member #7257 http://sfd.am-1.org/
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
