Gentoo Archives: gentoo-user

From: Rich Freeman <rich0@g.o>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] EAPI packages
Date: Tue, 16 Aug 2016 11:59:57
Message-Id: CAGfcS_k+JtwEvi1uu2vY9i2otknNJsyhp1ayvjXFWX5uW8w78w@mail.gmail.com
In Reply to: Re: [gentoo-user] EAPI packages by hw
1 On Tue, Aug 16, 2016 at 7:23 AM, hw <hw@×××××.de> wrote:
2 > Neil Bothwick schrieb:
3 >>
4 >> On Sat, 13 Aug 2016 16:08:34 +0200, hw wrote:
5 >>
6 >>> infrequently update Gentoo because I´m *always* running into problems
7 >>> like this.
8 >>
9 >> Every time, or is that just hyperbole?
10 >
11 > every time
12
13 Keep in mind that your reaction to problems with updates seems to be
14 to avoid updates and run them less frequently. However, this is the
15 sort of thing that is likely to make updates even more complicated to
16 resolve.
17
18 I tend to run most of my updates daily. Usually I run into no
19 problems, but occasionally I do (let's say once a month as a guess).
20 When I do run into a problem there are typically only a few packages
21 to be updated, so it is fairly obvious where the problems are coming
22 from. Usually somebody has already posted on a list or forum about
23 the issue, or there is a bug. If I end up fixing it myself it is a
24 lot easier to ID the issue when only a few packages are in scope.
25
26 However, if I ran an update once a year then I'd end up getting a list
27 of 500 packages to update, and probably about 12 different issues. I
28 wouldn't know which of those 500 packages are causing those 12 issues,
29 and I'd have to fix all 12 before the whole bolus is updated. I might
30 also run into circular dep issues since packages would have been
31 introduced to the tree, become dependencies, then been removed in the
32 time since my last update.
33
34 There are ways to do these kinds of updates but they're going to
35 require a lot of effort on your part to make them possible. You'd
36 probably want to set up your own repo to sync your production servers
37 from, and serve binary packages to reduce the build-time dependency
38 load. Plus, you probably don't want production machines building
39 packages anyway.
40
41 --
42 Rich