| 1 |
There's one thing that springs instantly to mind that uses a complex |
| 2 |
meta package that isnt a desktop environment is texlive. And jesus do |
| 3 |
the texlive team (all... two of them?) work hard. Special shout out. |
| 4 |
|
| 5 |
On Mon, 4 Oct 2021 at 16:37, Arve Barsnes <arve.barsnes@×××××.com> wrote: |
| 6 |
> |
| 7 |
> On Mon, 4 Oct 2021 at 08:05, <coalml@××××.io> wrote: |
| 8 |
> > 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? |
| 9 |
> |
| 10 |
> Probably depends on what you intend this 'meta' package to do. |
| 11 |
> Something like the KDE meta package is rarely useful outside of DE's |
| 12 |
> in my estimate, and exist purely to create a KDE 'package' that users |
| 13 |
> can easily install without much consideration. |
| 14 |
> |
| 15 |
> If you want to create your own groups of packages that you want to |
| 16 |
> install with a single command, I would look into sets. @system and |
| 17 |
> @world are sets that everyone uses, but it's easy to create your own |
| 18 |
> for whatever purpose. |
| 19 |
> |
| 20 |
> Portage is usually pretty good at helping you figure out any |
| 21 |
> dependency conflicts, so I wouldn't worry about it. Might be worth |
| 22 |
> looking deeper into the way portage prints dependency errors if you |
| 23 |
> encounter problems though. As evidenced by many a thread on this list, |
| 24 |
> it can sometimes be very hard to understand, simply because there can |
| 25 |
> be a lot of it when there are conflicts, and it's easy to get |
| 26 |
> side-tracked by information that isn't directly related to your |
| 27 |
> problem. |
| 28 |
> |
| 29 |
> > 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? |
| 30 |
> |
| 31 |
> You configure your repos in /etc/portage/repos.conf. For each repo you |
| 32 |
> have the option of setting a priority. I think "official third-party" |
| 33 |
> repos installed through layman gets a priority = 50, and if I'm not |
| 34 |
> mistaken, the official repo have a default of 100. If you want your |
| 35 |
> own repo to be the first choice, give your repo a higher priority. |
| 36 |
> |
| 37 |
> Cheers, |
| 38 |
> Arve |
| 39 |
> |
Archives