Hi y'all new confused user regarding package managementpretend all the time seems annoying on the long term as well so there should be lots of different solutions from different people(at least thats what I think)
How do you guys manage and protect your packages?
Do you just put everything on world and end up with a huge world file?
Do you have basic system files on world and the rest you protect or omit?
Do you create new(personalised) files depending on category and somehow link them in any of the above 3?
It's just emerging everything you are not sure you will keep with -1 seems cumbersome to me especially if at some point I want to transfer to a new device and want to copy my settings over ,select what to keep and discard the rest,depcleaning with
I just think this is one of the things its better I learn now rather than later and forum or wiki info is too "on-point" on a specific situation so I thought I'd ask the userbase
Hi y'all new confused user regarding package management
How do you guys manage and protect your packages?
Do you just put everything on world and end up with a huge world file?
Do you have basic system files on world and the rest you protect or omit?
Do you create new(personalised) files depending on category and somehow link them in any of the above 3?
It's just emerging everything you are not sure you will keep with -1 seems cumbersome to me especially if at some point I want to transfer to a new device and want to copy my settings over ,select what to keep and discard the rest,depcleaning withpretend all the time seems annoying on the long term as well so there should be lots of different solutions from different people(at least thats what I think)
Hi y'all new confused user regarding package management
How do you guys manage and protect your packages?
Do you just put everything on world and end up with a huge world file?
Do you have basic system files on world and the rest you protect or omit?
Do you create new(personalised) files depending on category and
somehow link them in any of the above 3?
It's just emerging everything you are not sure you will keep with -1
seems cumbersome to me especially if at some point I want to transfer
to a new device and want to copy my settings over ,select what to keep
and discard the rest,depcleaning with pretend all the time seems
annoying on the long term as well so there should be lots of different solutions from different people(at least thats what I think)
I just think this is one of the things its better I learn now rather
than later and forum or wiki info is too "on-point" on a specific
situation so I thought I'd ask the userbase
Hi y'all new confused user regarding package management
How do you guys manage and protect your packages?
Do you just put everything on world and end up with a huge world file?
Do you have basic system files on world and the rest you protect or omit?
Do you create new(personalised) files depending on category and
somehow link them in any of the above 3?
It's just emerging everything you are not sure you will keep with -1
seems cumbersome to me especially if at some point I want to transfer
to a new device and want to copy my settings over ,select what to keep
and discard the rest,depcleaning with pretend all the time seems
annoying on the long term as well so there should be lots of different solutions from different people(at least thats what I think)
I just think this is one of the things its better I learn now rather
than later and forum or wiki info is too "on-point" on a specific
situation so I thought I'd ask the userbase
As a example, if you want a
full KDE install, you just emerge the kde meta package and it gets
recorded in the world file. The emerge command will take care of all
the other packages that depend on the meta package. That is a LOT of packages too
On Mon, 4 Oct 2021 at 08:05, <> coalml@tuta.io> > wrote
Secondly(I know I will surely find this one in the wiki but)can I set a priority to pull from the local repo first if package exists and then have the official repo as a backup?
You configure your repos in /etc/portage/repos.conf. For each repo you
have the option of setting a priority. I think "official third-party"
repos installed through layman gets a priority = 50, and if I'm not
mistaken, the official repo have a default of 100. If you want your
own repo to be the first choice, give your repo a higher priority.
Cheers,
Arve
I would strongly, STRONGLY discourage you from creating your own meta package. There are very few meta packages in the tree (in the schemeinto that trap?
of things) for very good reasons, they take one hell of a lot of
maintenance. They're really only there for things like kde, where you
might just want a bare bones kde environment, or you might be
expecting the full-fat desktop environment with all the side packages
you'd get if you were using a distro that gave you no option out of
the box.
If you really want to group a bunch of packages into a set that gets
emerged with one command, I would do exactly that: create a custom
set. Similar to @world, @system, @security, etc. You can do that
quite easily, see https://wiki.gentoo.org/wiki/Package_sets .
But really there's not a lot of use cases for it, mostly if you use a
package and it's not just a dep of something (or several things) you
should just have it in your world file, *for most people's use cases*.
Going through your world file and cleaning out cruft is a part of
regular gentoo maintenance, should be done at a minimum annually imo.
Much like cleaning out distfiles and whatnot (see eclean, from app-portage/gentoolkit. And, indeed, pretty much every other useful
utility in gentoolkit. Also flaggie for use-flag management.)
On Mon, 4 Oct 2021 at 16:05, <coalml@tuta.io> wrote:
I thank the four of you for the insight I learn more in 5 mins then I did in an afternoon,I have two last question tho
As a example, if you want a
full KDE install, you just emerge the kde meta package and it gets
recorded in the world file. The emerge command will take care of all
the other packages that depend on the meta package. That is a LOT of
packages too
Theoretically I can make my own meta package and place in the localrepo I have and set it to pull packages from the official repos
Firstly is there any dependency hell that I can fall into when placing lots of different packages with (unexpectedly) conflicting deps on my own meta package?Has anyone (reading this) that has done it before and worked out a niche way to avoid falling
Secondly(I know I will surely find this one in the wiki but)can I set a priority to pull from the local repo first if package exists and then have the official repo as a backup?
Lastly thank you for your previous replies forgot to add it on my last mail and I didnt want to bloat the mailing list like im editing a forum post with asterisks :D
.
.
.
Thank you (ah I'm learning)
arve.barsnes@gmail.com</a>:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>On Mon, 4 Oct 2021 at 08:05, <<a href="mailto:coalml@tuta.io">coalml@tuta.io</a>> wrote<br></in /etc/portage/repos.conf. For each repo you<br></div><div>have the option of setting a priority. I think "official third-party"<br></div><div>repos installed through layman gets a priority = 50, and if I'm not<br></div><div>mistaken, the official repo
<blockquote>Secondly(I know I will surely find this one in the wiki but)can I set a priority to pull from the local repo first if package exists and then have the official repo as a backup?<br></blockquote><div><br></div><div>You configure your repos
<br></div><div>If you really want to group a bunch of packages into a set that gets<br></div><div>emerged with one command, I would do exactly that: create a custom<br></div><div>set. Similar to @world, @system, @security, etc. You can do that<br></package. That is a LOT of<br></div><div>packages too<br></div><div><br></div><div>Theoretically I can make my own meta package and place in the localrepo I have and set it to pull packages from the official repos<br></div><div><br></div><div>Firstly is
<div>quite easily, see https://wiki.gentoo.org/wiki/Package_sets .<br></div><div><br></div><div>But really there's not a lot of use cases for it, mostly if you use a<br></div><div>package and it's not just a dep of something (or several things) you<
</div><div>should just have it in your world file, *for most people's use cases*.<br></div><div>Going through your world file and cleaning out cruft is a part of<br></div><div>regular gentoo maintenance, should be done at a minimum annually imo.<br></
<div>Much like cleaning out distfiles and whatnot (see eclean, from<br></div><div>app-portage/gentoolkit. And, indeed, pretty much every other useful<br></div><div>utility in gentoolkit. Also flaggie for use-flag management.)<br></div><div><br></
<div>On Mon, 4 Oct 2021 at 16:05, <coalml@tuta.io> wrote:<br></div><blockquote><div><br></div><div>I thank the four of you for the insight I learn more in 5 mins then I did in an afternoon,I have two last question tho<br></div><div><br></div><
As a example, if you want a<br></div><div>full KDE install, you just emerge the kde meta package and it gets<br></div><div>recorded in the world file. The emerge command will take care of all<br></div><div>the other packages that depend on the meta
<br></div></blockquote></blockquote><div dir="auto"><br></div> </body> </html>
Firstly is there any dependency hell that I can fall into when placing lots of different packages with (unexpectedly) conflicting deps on my own meta package?Has anyone (reading this) that has done it before and worked out a niche way to avoid fallinginto that trap?
Secondly(I know I will surely find this one in the wiki but)can I set a priority to pull from the local repo first if package exists and then have the official repo as a backup?
I thank the four of you for the insight I learn more in 5 mins then I did in an afternoon,I have two last question thointo that trap?
As a example, if you want a
full KDE install, you just emerge the kde meta package and it gets
recorded in the world file. The emerge command will take care of all
the other packages that depend on the meta package. That is a LOT of packages too
Theoretically I can make my own meta package and place in the localrepo I have and set it to pull packages from the official repos
Firstly is there any dependency hell that I can fall into when placing lots of different packages with (unexpectedly) conflicting deps on my own meta package?Has anyone (reading this) that has done it before and worked out a niche way to avoid falling
Secondly(I know I will surely find this one in the wiki but)can I set a priority to pull from the local repo first if package exists and then have the official repo as a backup?
Lastly thank you for your previous replies forgot to add it on my last mail and I didnt want to bloat the mailing list like im editing a forum post with asterisks :D
.
.
.
Thank you (ah I'm learning)
On Mon, 4 Oct 2021 at 08:05, <coalml@tuta.io> wrote:falling into that trap?
Firstly is there any dependency hell that I can fall into when placing lots of different packages with (unexpectedly) conflicting deps on my own meta package?Has anyone (reading this) that has done it before and worked out a niche way to avoid
Probably depends on what you intend this 'meta' package to do.
Something like the KDE meta package is rarely useful outside of DE's
in my estimate, and exist purely to create a KDE 'package' that users
can easily install without much consideration.
If you want to create your own groups of packages that you want to
install with a single command, I would look into sets. @system and
@world are sets that everyone uses, but it's easy to create your own
for whatever purpose.
Portage is usually pretty good at helping you figure out any
dependency conflicts, so I wouldn't worry about it. Might be worth
looking deeper into the way portage prints dependency errors if you
encounter problems though. As evidenced by many a thread on this list,
it can sometimes be very hard to understand, simply because there can
be a lot of it when there are conflicts, and it's easy to get
side-tracked by information that isn't directly related to your
problem.
Secondly(I know I will surely find this one in the wiki but)can I set a priority to pull from the local repo first if package exists and then have the official repo as a backup?
You configure your repos in /etc/portage/repos.conf. For each repo you
have the option of setting a priority. I think "official third-party"
repos installed through layman gets a priority = 50, and if I'm not
mistaken, the official repo have a default of 100. If you want your
own repo to be the first choice, give your repo a higher priority.
Cheers,
Arve
If you really want to group a bunch of packages into a set that gets
emerged with one command, I would do exactly that: create a custom
set. Similar to @world, @system, @security, etc. You can do that
quite easily, see https://wiki.gentoo.org/wiki/Package_sets .
As you can see from the two earlier replies, from cal and Dale, this
depends on how you want to manage your system. If you do a lot of
installing, putting -1 in your defaults might be the way to go, but personally I'm in cal's camp, I would much rather remember the -1 when
I'm doing something ad hoc, and have any programs I want added to
world without adding another flag to my emerge command.
As for depclean, I have added an alias for depclean with --pretend
that I use after world updates. Unless you have installed something
with -1, most of the time that list is empty. And the output gives
nice clean lists of what packages it wants to remove, with exact
version strings and slots, so if I agree, I just do 'emerge -C <copied
list>' and I'm good to go.
On Mon, 4 Oct 2021 06:31:53 +0200, Arve Barsnes wrote:
As for depclean, I have added an alias for depclean with --pretend
that I use after world updates. Unless you have installed something
with -1, most of the time that list is empty. And the output gives
nice clean lists of what packages it wants to remove, with exact
version strings and slots, so if I agree, I just do 'emerge -C <copied list>' and I'm good to go.
Why not use --ask instead of --pretend? Then you don't have to copy
anything or re-run commands. "emerge -ca" is short enough to not need an alias.
Lol i just installed that earlier, didnt know gentoo is THAT understaffed,looking at the history i know of i still dont understand if
the wiki dying was a good or a bad thing for the community in one hand hardcore fans stayed and rewrote(of what i can see) some epic documentation in comparison to other distors,on the other hand. . .
I would strongly, STRONGLY discourage you from creating your own meta package. There are very few meta packages in the tree (in the scheme
of things) for very good reasons, they take one hell of a lot of
maintenance. They're really only there for things like kde, where you
might just want a bare bones kde environment, or you might be
expecting the full-fat desktop environment with all the side packages
you'd get if you were using a distro that gave you no option out of
the box.
If you really want to group a bunch of packages into a set that gets
emerged with one command, I would do exactly that: create a custom
set. Similar to @world, @system, @security, etc. You can do that
quite easily, see https://wiki.gentoo.org/wiki/Package_sets .
But really there's not a lot of use cases for it, mostly if you use a
package and it's not just a dep of something (or several things) you
should just have it in your world file, *for most people's use cases*.
Going through your world file and cleaning out cruft is a part of
regular gentoo maintenance, should be done at a minimum annually imo.
Much like cleaning out distfiles and whatnot (see eclean, from app-portage/gentoolkit. And, indeed, pretty much every other useful
utility in gentoolkit. Also flaggie for use-flag management.)
Why not use --ask instead of --pretend? Then you don't have to copy anything or re-run commands. "emerge -ca" is short enough to not need
an alias.
Mostly because, while I am not a prolific installer of temporary
packages, I fairly often (compared to how often depclean wants to
remove anything at all) have one or two packages in the list that I
want to delay removing for a little while. Most common after a kernel
upgrade where I still have not gotten around to reboot and confirm
that the new version actually works. Copying the package list now and
then seems less of a hassle to me than having to say no to --ask most
of the time.
On Mon, 4 Oct 2021 10:33:58 +0200, Arve Barsnes wrote:
I picked up this tip some years ago to avoid depcleaning kernel sources.
% cat /etc/portage/sets.conf
[kernels]
class = portage.sets.dbapi.OwnerSet
world-candidate = False
files = /usr/src
and emerge -n @kernels
On Mon, 4 Oct 2021 10:33:58 +0200, Arve Barsnes wrote:
I picked up this tip some years ago to avoid depcleaning kernel
sources.
% cat /etc/portage/sets.conf
[kernels]
class = portage.sets.dbapi.OwnerSet
world-candidate = False
files = /usr/src
and emerge -n @kernels
I also have this in the file to allow multiple GCC versions.
[gcc]
class = portage.sets.dbapi.OwnerSet
world-candidate = False
files = /usr/x86_64-pc-linux-gnu/gcc-bin
On Mon, 4 Oct 2021 10:33:58 +0200, Arve Barsnes wrote:
I picked up this tip some years ago to avoid depcleaning kernel
sources.
% cat /etc/portage/sets.conf
[kernels]
class = portage.sets.dbapi.OwnerSet
world-candidate = False
files = /usr/src
and emerge -n @kernels
Interesting way to do it. I want them depcleaned though, as soon as I
confirm that the new kernel works as expected. I use a custom
patch-set, so I never have any updates unless I add them myself, so
I'm not sure if using a set would give me anything.
On Mon, 4 Oct 2021 21:31:35 +0200, Arve Barsnes wrote:
Fair enough. I use standard gentoo-sources but always like to keep atOn Mon, 4 Oct 2021 10:33:58 +0200, Arve Barsnes wrote:Interesting way to do it. I want them depcleaned though, as soon as I
I picked up this tip some years ago to avoid depcleaning kernel
sources.
% cat /etc/portage/sets.conf
[kernels]
class = portage.sets.dbapi.OwnerSet
world-candidate = False
files = /usr/src
and emerge -n @kernels
confirm that the new kernel works as expected. I use a custom
patch-set, so I never have any updates unless I add them myself, so
I'm not sure if using a set would give me anything.
least one previous version available "just in case". I unmerge old
versions manually, I have to delete kernel sources manually anyway as
emerge only removes the files it installed, leaving all the files created when compiling the kernel.
On Mon, 4 Oct 2021 18:02:55 -0500, Dale wrote:
When I checked it in the pastFair enough. I use standard gentoo-sources but always like to keep atI "borrowed" your method a good while back and do it the same way. Even
least one previous version available "just in case". I unmerge old
versions manually, I have to delete kernel sources manually anyway as
emerge only removes the files it installed, leaving all the files
created when compiling the kernel.
if I use emerge to remove it, it always leaves cruft behind so I just do
it manually then tell emerge to remove it from its info.Â
rm -fr /usr/src/linux-version
emerge -C gentoo-sources-version
was significantly faster than
emerge -C gentoo-sources-version
rm -fr /usr/src/linux-version
Fair enough. I use standard gentoo-sources but always like to keep at
least one previous version available "just in case". I unmerge old
versions manually, I have to delete kernel sources manually anyway as emerge only removes the files it installed, leaving all the files
created when compiling the kernel.
I "borrowed" your method a good while back and do it the same way. Even
if I use emerge to remove it, it always leaves cruft behind so I just do
it manually then tell emerge to remove it from its info.Â
When I checked it in the past
rm -fr /usr/src/linux-version
emerge -C gentoo-sources-version
was significantly faster than
emerge -C gentoo-sources-version
rm -fr /usr/src/linux-version
On Mon, 4 Oct 2021 18:02:55 -0500, Dale wrote:> rm -fr /usr/src/linux-version emerge -C gentoo-sources-version
was significantly faster than
emerge -C gentoo-sources-version
rm -fr /usr/src/linux-version
On Tuesday, 5 October 2021 00:11:42 BST Neil Bothwick wrote:
When I checked it in the past
rm -fr /usr/src/linux-version
emerge -C gentoo-sources-version
was significantly faster than
emerge -C gentoo-sources-version
rm -fr /usr/src/linux-version
Yes, it would be. The first way, portage just scans the list of files and tries
to delete what isn't there; the second way it actually has to delete real files.
Yes, it would be. The first way, portage just scans the list of filesI doubt that's the problem. After all, rm has to delete the files too.
and tries to delete what isn't there; the second way it actually has
to delete real files.
I guess portage scans the files and looks up whether it can delete them
or not. If you've deleted them already, that step no longer happens ...
was significantly faster than
emerge -C gentoo-sources-versionSo what about other packages? Do you guys find it faster to
rm -fr /usr/src/linux-version
rm -rf $(equary f PACKAGE) && emerge -C PACKAGE? Is that slower cuz
equery is also called or could that cause unwanted files from other
packages to be wiped?maybe filters?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 44:23:39 |
| Calls: | 6,648 |
| Files: | 12,197 |
| Messages: | 5,329,704 |