6:11 a.m.
scanned the dnf man page, did not see an immediate solution so i'll
ask here:
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? on more
than one occasion, i've had to install dozens (or hundreds) of
packages, *knowing* that i would need them only for a while, at which
time it would be nice to be able to remove them all via 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="new_project"
is there anything like this? (and, yes, i can appreciate the
possibility for conflicts when an initially "tagged" package would
later be installed explicitly, and so on.)
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
r
6:15 a.m.
New subject: dnf: can i "tag" installed packages so i can remove them
later?
On Sat, 14 Jul 2018, Robert P. J. Day wrote:
scanned the dnf man page, did not see an immediate solution so i'll
ask here:
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? on more
than one occasion, i've had to install dozens (or hundreds) of
packages, *knowing* that i would need them only for a while, at which
time it would be nice to be able to remove them all via 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="new_project"
whoops, that should have of course said:
$ sudo dnf remove --tag="my_project"
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
8:33 a.m.
On 07/14/18 19:11, Robert P. J. Day wrote:
scanned the dnf man page, did not see an immediate solution so
i'll
ask here:
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? on more
than one occasion, i've had to install dozens (or hundreds) of
packages, *knowing* that i would need them only for a while, at which
time it would be nice to be able to remove them all via 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="new_project"
is there anything like this? (and, yes, i can appreciate the
possibility for conflicts when an initially "tagged" package would
later be installed explicitly, and so on.)
I don't quite understand what you are after.
If you install a package and it pulls in a bunch of dependencies and then you remove
it the dependencies will also be removed unless you've installed additional packages
which require them.
dnf install erlang
.
.
.
Transaction Summary
===================================================================================
Install 67 Packages
Total download size: 79 M
Installed size: 208 M
Is this ok [y/N]:
dnf remove erlang
.
.
.
Transaction Summary
===================================================================================
Remove 67 Packages
Freed space: 208 M
Is this ok [y/N]:
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
12:11 p.m.
New subject: dnf: can i "tag" installed packages so i can remove them
later?
On Sat, 14 Jul 2018, Ed Greshko wrote:
On 07/14/18 19:11, Robert P. J. Day wrote:
> scanned the dnf man page, did not see an immediate solution so i'll
> ask here:
>
> 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? on more
> than one occasion, i've had to install dozens (or hundreds) of
> packages, *knowing* that i would need them only for a while, at which
> time it would be nice to be able to remove them all via 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="new_project"
>
> is there anything like this? (and, yes, i can appreciate the
> possibility for conflicts when an initially "tagged" package would
> later be installed explicitly, and so on.)
>
I don't quite understand what you are after...
then perhaps you should have taken the time to figure it out before
posting an answer. it's just a thought.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
2:21 p.m.
On 07/15/18 01:11, Robert P. J. Day wrote:
then perhaps you should have taken the time to figure it out
before
posting an answer. it's just a thought.
OK, now I know how to adjust my filters.
Pardon me for attempting to help.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
9:08 a.m.
Robert P. J. Day wrote:
scanned the dnf man page, did not see an immediate solution so i'll
ask here:
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? on more
than one occasion, i've had to install dozens (or hundreds) of
packages, *knowing* that i would need them only for a while, at which
time it would be nice to be able to remove them all via 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
sudo dnf history undo ...
may be of use here (you can undo individual transactions
-- Rex
12:16 p.m.
New subject: dnf: can i "tag" installed packages so i can remove them
later?
On Sat, 14 Jul 2018, Rex Dieter wrote:
Robert P. J. Day wrote:
>
> scanned the dnf man page, did not see an immediate solution so i'll
> ask here:
>
> 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? on more
> than one occasion, i've had to install dozens (or hundreds) of
> packages, *knowing* that i would need them only for a while, at which
> time it would be nice to be able to remove them all via 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
sudo dnf history undo ...
may be of use here (you can undo individual transactions
sort of, but still not exactly what i'm after. it might be that i'm
trying to install packages for a completely new project, and all of
this is not going to happen all at once, i do it little by little as i
figure out which new components i need (and those components might be
entirely unrelated in terms of functionality).
ideally, what i want is the equivalent of on-the-fly defining a new
"group" of RPMs, and associating selected RPMs that i install with
that new group, but i'm fairly convinced that no such feature exists,
so i'll mock something up. or fake it somehow.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
1:42 p.m.
On Jul 14, 2018, at 6:11 AM, Robert P. J. Day <rpjday(a)crashcourse.ca> 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=“new_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.
good luck,
Bev in TX
2:30 p.m.
New subject: dnf: can i "tag" installed packages so i can remove them
later?
On Sat, 14 Jul 2018, Bev in TX wrote:
On Jul 14, 2018, at 6:11 AM, Robert P. J. Day
<rpjday(a)crashcourse.ca> 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
========================================================================
3:31 p.m.
On 07/14/2018 12:30 PM, Robert P. J. Day wrote:
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?
Generally, if I need to install something, I'll probably use it again
later. And even if not, the disk space used is irrelevant. Of course,
in the case that it is something really big (like debuginfo), it's easy
to find and remove.
1:46 a.m.
Hi.
On Sat, 14 Jul 2018 15:30:36 -0400 "Robert P. J. Day" wrote:
> 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.
Complicated. See below.
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 ...
Why?
Keeping track of those packages will allow easily to:
- memorize what your project needs
- deploy those packages on other machines
- suppress them
You can for example maintain a plain file containing only their names:
my_project_rpms.txt
Then install by using only:
dnf install $(< my_project_rpms.txt)
and remove with:
dnf remove $(< my_project_rpms.txt)
No need IMO of a special option to dnf for that.
--
francis
11:52 a.m.
On Sat, 14 Jul 2018 15:30:36 -0400, Robert P. J. Day wrote inter alia:
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?
I do something like that. It works, fairly conveniently on the
scale I use it, and maybe it will on yours.
su or sudo to root on two different tabs on your terminal. Start
your install (or update) on one, and pause when it asks yes or no.
C&p the things you don't want, or won't want for long, to "dnf
remove" on the second tab, but DO NOT hit enter. Repeat as needed. Let
the full install go through.
If there are many rpms on the second tab, c&p to a text file. Hit
enter on the remove command; and look carefully on what it will take with
it. If there are many removals, abort the remove, and go through your
text file individually.
Now reverse the procedure: during remove(s), c&p anything you
need, and try installing it alone after the remove(s).
All the above sounds like a lot more trouble than it actually is,
thanks to cyber-speed, IF you're doing it on the scale I am. Whether it's
worth the stuff you mean, I can't guess.
--
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
12:06 a.m.
On Sat, Jul 14, 2018 at 07:11:32AM -0400, Robert P. J. Day wrote:
scanned the dnf man page, did not see an immediate solution so i'll
ask here:
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? on more
than one occasion, i've had to install dozens (or hundreds) of
packages, *knowing* that i would need them only for a while, at which
time it would be nice to be able to remove them all via 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="new_project"
is there anything like this? (and, yes, i can appreciate the
possibility for conflicts when an initially "tagged" package would
later be installed explicitly, and so on.)
I see a file "/var/lib/dnf/groups.json" that seems to list
the group names and their packages.
If that file is used by dnf, then perhaps you could
create and manage your own group.
jl
--
Jon H. LaBadie jonfu(a)jgcomp.com
1:48 p.m.
On Sun, 15 Jul 2018 01:06:22 -0400
Jon LaBadie <jonfu(a)jgcomp.com> wrote:
On Sat, Jul 14, 2018 at 07:11:32AM -0400, Robert P. J. Day wrote:
>
> scanned the dnf man page, did not see an immediate solution so
> i'll ask here:
>
> 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? on more
> than one occasion, i've had to install dozens (or hundreds) of
> packages, *knowing* that i would need them only for a while, at
> which time it would be nice to be able to remove them all via 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="new_project"
>
> is there anything like this? (and, yes, i can appreciate the
> possibility for conflicts when an initially "tagged" package would
> later be installed explicitly, and so on.)
>
I see a file "/var/lib/dnf/groups.json" that seems to list
the group names and their packages.
If that file is used by dnf, then perhaps you could
create and manage your own group.
Or maybe something like this would be of use:
"sudo dnf install docker | tee docker_project_install.log"
and maybe include the -a switch if you want to add something to the same log.
Or a virtual machine you could delete after use?
12:23 a.m.
Il 14/07/2018 13:11, Robert P. J. Day ha scritto:
scanned the dnf man page, did not see an immediate solution so i'll
ask here:
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? on more
than one occasion, i've had to install dozens (or hundreds) of
packages, *knowing* that i would need them only for a while, at which
time it would be nice to be able to remove them all via 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="new_project"
is there anything like this? (and, yes, i can appreciate the
possibility for conflicts when an initially "tagged" package would
later be installed explicitly, and so on.)
rday
Have you considered simply creating an empty RPM called, say,
myproject1.rpm, which references the RPMs you need? When done simply
uninstall it.
2108
days inactive
2113
days old
14 comments
10 participants
participants (10)
-
Beartooth -
Bev in TX -
Ed Greshko -
Francis.Montagnac＠inria.fr -
Fred Erickson -
Jon LaBadie -
Mayavimmer -
Rex Dieter -
Robert P. J. Day -
Samuel Sieb