On Mon, Apr 23, 2012 at 09:13:23PM +0200, Adrian Schröter wrote:
Am Montag, 23. April 2012, 16:02:25 schrieb Claudio Freire:
On Mon, Apr 23, 2012 at 3:51 PM, Greg Freemyer
wrote: People tend to branch it instead of adding an _aggregate so a change in the original package triggers lots of other packages.
Regards.
It's down to 23 builds 4 hours later, so at least they are not in an infinite loop.
If trying to recover some OBS resources, llvm seems like a package worth trying kill off some branches / build repos.
I think the problem is that the wiki recommends not to use aggregates, which seems counterintuitive.
aggregates are indeed only recommended for very extreme cases. And you need know exactly the disadvantages of it.
Many timas an aggregate is better than a source link, though. Source links/branches are even worse than aggregates.
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
On 04/24/2012 11:43 AM, Michael Schroeder wrote: provide this dependency to your users alongside? IMO this makes only sense for statically linked stuff. On the other hand, aggregates tend to break ever so often, thus you're always on the safe side by using links only. They're a rather simple 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. my 2 cents. -- Viele Grüße, Sascha Peilicke