Mailinglist Archive: opensuse-buildservice (232 mails)

< Previous Next >
Re: [opensuse-buildservice] overwhelmed by llvm builds?
  • From: Sascha Peilicke <saschpe@xxxxxx>
  • Date: Tue, 24 Apr 2012 12:33:08 +0200
  • Message-id: <>
On 04/24/2012 12:02 PM, Michael Schroeder wrote:
On Tue, Apr 24, 2012 at 11:53:06AM +0200, Sascha Peilicke wrote:
But most of the time the correct solution is to just put
the repository with the needed packages in the path. You need
aggregates/source links only if
- the other packages from the repository break your build, or
- you need to have the packages in your published repo.
Right, which is IMO almost always the case. I can't come up with a case
where you would want to build against a certain package but don't
provide this dependency to your users alongside?

Well, you don't aggregate every Factory package, do you? And
with "One Click Install", you also get the other repositories
added to your system, which is much cleaner than duplicating
binary packages.

IMO this makes only
sense for statically linked stuff. On the other hand, aggregates tend to
break ever so often

They break? Why? How?
People changing repo names and forgetting to add new repos (for new
releases) mainly.

thus you're always on the safe side by using links
only. They're a rather simple concept,

Yes, a simple and dumb concept.

always get a rebuild and a
publish. IMO this should remain the only way we advertise to packagers,
the other stuff breaks just too often. Also, users shouldn't care which
is faster, this is our problem to solve, not theirs.

I don't think rebuilding the universe is really our goal.
True, but that's what we're doing all the time no? To me it's more a
practical choice, I used to use aggregates a lot but it involved a lot
of communication with other project maintainers and adjustment whenever
a new openSUSE release was out. Links don't have that issue, and with my
packager hat on, I don't care in which project the binary was built.
Viele Grüße,
Sascha Peilicke

< Previous Next >