On Mon, Apr 23, 2012 at 1:56 PM, Ismail Doenmez wrote:

Hi;

Quoting Greg Freemyer :

...

All,

I just happened to look at the OBS status monitor page a few hours.  I did a quick count of llvm build jobs currently in progress.  Then I checked again just now.

Both times it was about 40 currently building build jobs and that does not include llvm-clang, llvm-latest,  etc  So that's about 40 llvm builds that have been running for several hours..

I don't know if that is reasonable or not, but I've never noticed one package dominating the build farm like that before.

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. Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

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. In best case just build against the other repository, so build against devel:tools:compiler/$repo instead of copying the binaries. It does not waste disk space, does not require re-signing and will not break when the other packager decides to play with dependencies. use a branch, when you need build it in a different way (eg. for another distribution or with some source change). bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Mon, Apr 23, 2012 at 04:55:44PM -0300, Claudio Freire wrote:

On Mon, Apr 23, 2012 at 4:13 PM, Adrian Schröter wrote:

...

aggregates are indeed only recommended for very extreme cases. And you need know exactly the disadvantages of it.

In best case just build against the other repository, so build against devel:tools:compiler/$repo instead of copying the binaries. It does not waste disk space, does not require re-signing and will not break when the other packager decides to play with dependencies.

use a branch, when you need build it in a different way (eg. for another distribution or with some source change).

Well, none of that was in the wiki last time I checked, especially the bits about how not to waste disk space or re-signing.

Then it would be great if one add the explanation Adrian has given to the wiki article. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

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. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

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?

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. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On 4/24/2012 5:43 AM, Michael Schroeder wrote:

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.

Cheers, Michael.

You are very cavalier with those terms like better and worse and correct and "most of the time". Where does this magic knowledge come from that you know what is correct most of the time? You really know all the factors involved in everyones obs projects? That's amazing! For myself, I'm not as omniscient as you. I can only know about my own project and you are wrong for that one. But hey maybe everyone else uses obs for some different reasons than I do, and so you could still be right overall. Aggregate is "better" than a link in the way that a bicycle is better than a car. It's cheaper to build, cheaper to ship, cheaper to run. But none of that matters if the job that needs doing can't be done by a bicycle. -- bkw -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org