Re: dnf: can i "tag" installed packages so i can remove them later?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 14 Jul 2018, Bev in TX wrote:

> On Jul 14, 2018, at 6:11 AM, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote:
> > ...
> >  is there any way to dynamically tag or label packages during dnf
> > install so i can remove them all later by that tag or label? ...
> >
> >  i guess i'm after something i would think of as a "dynamic group",
> > where i could run, say:
> >
> >  $ sudo dnf install --tag="my_project" docker
> >  $ sudo dnf install --tag="my_project" erlang
> >
> > and possibly other totally unrelated packages, then toss them all
> > later with:
> >
> >  $ sudo dnf remove --tag=“my_project” …

> I’m a newbie so I can’t respond about the intricacies of the dnf
> command.  However, if no one else provides a solution and you have
> not already done so, you might consider writing a script to do the
> removes for you.  At its simplist, you could create a script named
> “dnf_remove_my_project” with lines:
>
> dnf remove docker
> dnf remove erlang
> ...
>
> and then use:
>
> sudo dnf_remove_my_project
>
> You could get fancy, such as having a script, eg dnf_group, that
> does the dnf install and create/append to the dnf_remove_my_project
> script.

  except the whole point of this exercise is that i don't want to have
to manually keep track of the packages as i install them.  as i am
installing everything for this new "project", i was asking for a way
to somehow tag or label each "dnf install" command such that,
subsequently, i could collectively undo/remove all of them once i was
completely finished and had no further use for the project.

  i accept there is no such current functionality in dnf, and i
realize it sounds like a weird request, but has no one else ever gone
through this -- installing one RPM after another (plus its
dependencies) as you identify which other packages you need to do
something? and after it's all over, you'd love to get rid of all that
stuff you don't need anymore?

rday

p.s. maybe it's time for me to learn how to write a dnf plug-in, since
it doesn't sound like it would be that difficult.

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                  http://crashcourse.ca/dokuwiki

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/WIP5USHWAY76FLGJRBXZSWNGNMOWUPFI/
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux