Hi,
thanks for your answer.
$ : non root prompt
# : root prompt
- Problem using add-user-tag :
the following command does not complain (in non root prompt). I have no
special multi-arch system (AFAIK) :
$ aptitude add-user-tag test emacs
then the following command does not succeed (gives nothing) :
$ aptitude search '?user-tag(test)'
To make it work, I need to be root. Which is ok, but I should have
received a warning or an error, right?
As root :
# aptitude add-user-tag test emacs
then no mater root or not, it works :
$ aptitude search '?user-tag(test)'
- get a command to list active user tags, such as :
$ aptitude show-user-tags
or :
$ aptitude show user-tag
- get a command to search packages and see their tags :
$ aptitude search em
i emacs test,foo
i emfoo bar
i barem other-tag
Thanks a lot for your answer. The given command gives 1225 packages :
$ aptitude search '~i!~M'
In my case, such a list is clearly not manageable! The ubuntu command :
aptitude search
'~i!~M(!~tubuntu-desktop!~tminimal!~tstandard!~tprint-server)(!~n^grub$!~n^linux-!~n^aspell$!~n^openoffice.org-l10n-common$((!~n-fr$!~n-fr-)|~ndoc-fr$))'
gives 103 packages, which starts to become manageable!
So, clearly, having a command such as this one, given in the man page, that
would give the 103 packages, would be very interesting :
$ aptitude search ~user
But I can fully understand that aptitude is not able to do it. Indeed, that
would require a definition of what is from the distribution and what is not,
which does not seam easy.
The old style tasks have been phased out and replaced by meta-packages
with names beginning with "task-". As a result of this it is now
possible to have the dependencies of a task marked as automatically
installed and thus most of the clutter in your preferred search
("!~tubuntu-desktop" etc.) will no longer be needed. However, if you had
upgraded from an older system it is likely you will have to select each
task that is installed and mark the dependencies before this is useful.
I don't believe it will be worth anyone's effort to attempt to define a
"distribution/non-distribution" distinction between packages.
"However, if you had upgraded from an older system it is likely you will
have to select each task that is installed and mark the dependencies
before this is useful" : Could you please be more specific on the
commands to run ?
- with all your combined answers, I will try to update the debian wiki
with a few well thought commands...
Thanks,
William
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
