[opensuse-buildservice] _aggregate and web interface
Hello, I tried to remove some build load from BuildService and implemented _aggregate instead of _link in some of the things I do. Really nice. Now a suggestion for the web interface: a) On the "New Package Link in Project xxx" page add a checkmark "No rebuild, file copy only (aggregate)" which produce _aggregate file instead of _link b) On the project page add also for aggregates: This package links to the sources of the package xxx of project xxx. c) On the project page mark the _aggregate file like the _link file is marked in the Files-section. Why? I think the feature is very helpful, but much too seldom used. Two main advantages I see: - Reduced buildservice load - Equal packages versions in the download area for equal packages (less user confusion). BTW: Is reducing the download space possible using softlinks for _aggregate? Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 8/13/07, Dirk Stoecker <opensuse@dstoecker.de> wrote:
Hello,
I tried to remove some build load from BuildService and implemented _aggregate instead of _link in some of the things I do. Really nice.
Yes, the idea is really nice. I have a suggestion, to make it really useful, _aggregate need to act as _link for the missing targets and build package for those targets that are missing from originating repository. Thanks Jigish --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
CyberOrg escribió:
I have a suggestion, to make it really useful, _aggregate need to act as _link for the missing targets and build package for those targets that are missing from originating repository.
see http://build.opensuse.org/package/edit_file?file=_aggregate&package=GeoIP&pr... for an example how to do that. -- WARNING: This bug is visible only to employees, You are allowed to be mad at them.
On 8/16/07, Cristian Rodriguez <crrodriguez@suse.de> wrote:
CyberOrg escribió:
I have a suggestion, to make it really useful, _aggregate need to act as _link for the missing targets and build package for those targets that are missing from originating repository. see http://build.opensuse.org/package/edit_file?file=_aggregate&package=GeoIP&pr... for an example how to do that.
Cool, thank you. -J --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, 16 Aug 2007, Cristian Rodriguez wrote:
CyberOrg escribió:
I have a suggestion, to make it really useful, _aggregate need to act as _link for the missing targets and build package for those targets that are missing from originating repository.
see
http://build.opensuse.org/package/edit_file?file=_aggregate&package=GeoIP&pr...
for an example how to do that.
I don't see your point here. All the targets you use are also in your source. You only copy some binaries to strongly related targets. The problem described above is like this. Source has e.g. openSUSE_10.2. My aggregate package has openSUSE_10.2 and SUSE_Linux_10.0. How can I fill the 10.0 with packages (assuming the package can build with 10.0)? Copying the package from 10.2 to 10.0 like in your GeoIP is no option. Ciao -- http://www.dstoecker.eu/ (PGP key available)
participants (3)
-
Cristian Rodriguez
-
CyberOrg
-
Dirk Stoecker