1 |
I would strongly, STRONGLY discourage you from creating your own meta |
2 |
package. There are very few meta packages in the tree (in the scheme |
3 |
of things) for very good reasons, they take one hell of a lot of |
4 |
maintenance. They're really only there for things like kde, where you |
5 |
might just want a bare bones kde environment, or you might be |
6 |
expecting the full-fat desktop environment with all the side packages |
7 |
you'd get if you were using a distro that gave you no option out of |
8 |
the box. |
9 |
|
10 |
If you really want to group a bunch of packages into a set that gets |
11 |
emerged with one command, I would do exactly that: create a custom |
12 |
set. Similar to @world, @system, @security, etc. You can do that |
13 |
quite easily, see https://wiki.gentoo.org/wiki/Package_sets . |
14 |
|
15 |
But really there's not a lot of use cases for it, mostly if you use a |
16 |
package and it's not just a dep of something (or several things) you |
17 |
should just have it in your world file, *for most people's use cases*. |
18 |
Going through your world file and cleaning out cruft is a part of |
19 |
regular gentoo maintenance, should be done at a minimum annually imo. |
20 |
Much like cleaning out distfiles and whatnot (see eclean, from |
21 |
app-portage/gentoolkit. And, indeed, pretty much every other useful |
22 |
utility in gentoolkit. Also flaggie for use-flag management.) |
23 |
|
24 |
On Mon, 4 Oct 2021 at 16:05, <coalml@××××.io> wrote: |
25 |
> |
26 |
> 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 |
27 |
> |
28 |
> As a example, if you want a |
29 |
> full KDE install, you just emerge the kde meta package and it gets |
30 |
> recorded in the world file. The emerge command will take care of all |
31 |
> the other packages that depend on the meta package. That is a LOT of |
32 |
> packages too |
33 |
> |
34 |
> 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 |
35 |
> |
36 |
> 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 into that trap? |
37 |
> |
38 |
> 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? |
39 |
> |
40 |
> 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 |
41 |
> . |
42 |
> . |
43 |
> . |
44 |
> Thank you (ah I'm learning) |
45 |
> |
46 |
> |
47 |
> |