Mailinglist Archive: opensuse-buildservice (266 mails)

< Previous Next >
Re: [opensuse-buildservice] Minimal server
  • From: Richard Bos <rbos@xxxxxxxxxxxx>
  • Date: Fri, 14 Nov 2008 23:34:12 +0100
  • Message-id: <200811142334.12783.rbos@xxxxxxxxxxxx>
Hi,

Op Friday 14 November 2008 10:07:30 schreef u:
Please keep in mind: every duplicate package is wasting space and
cpu-cycles. If you just import packages, but have no patch or other
changes, use _aggregate. If there's no change, why it should get
rebuilt ? (Thats what _link would do.)

Because of the confusing comment on the wiki
http://en.opensuse.org/Build_Service/Tips_and_Tricks#The_difference_betwe
en __link_and__aggregate "Aggregate is possible, but slows down your build
and requires double space. Better build directly against the other
repository." I don't use aggregate....  Is the comment correct, about the
slower builds and double file space????  As the packages are already
build, I would expect that aggregated are not build at all.

Yes, it is correct. If you do not want to copy it than do not aggregate ;)
But just build against the other repository as suggested.

That's all nice, but in this wiki section about "The difference between _link
and _aggregate", nowhere is building against another repository mentioned.
From that point of view, the comment is not given on the right location.

Perhaps the section should also talk about "building against another
repository", to make the section more complete? If so the table can show the
all the differences between:
project _link _aggregate

When to use aggregate and when to use "build against repository". Is it for 1
or 2 packages use aggregate if more than use "build against repository"?


--
Richard
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >