I have a question about Plague. Does Plague have the capability to handle dependencies where if you build one RPM that other RPMS depend on for their BuildRequires that you can then build all those RPMS and any other RPMS which maybe affected by building them?
Say I have a package: base.
I also have package: dep1 and dep2 which both Require base and BuildRequire base.
I have another package: dep-11 which Requires dep1,base and BuildRequires dep1,base
I rebuild base in Plague and I would like a way to then automatically rebuild dep1 and dep2. And then rebuild dep-11.
Thanks for any help, John
On Tue, 2007-03-27 at 19:56 -0700, John Villalovos wrote:
I have a question about Plague. Does Plague have the capability to handle dependencies where if you build one RPM that other RPMS depend on for their BuildRequires that you can then build all those RPMS and any other RPMS which maybe affected by building them?
ie, like debian's build system?
No, plague doesn't do that. It was a planned option but Koji is taking over for plague and I'm not sure if that's planned for Koji.
Dan
Say I have a package: base.
I also have package: dep1 and dep2 which both Require base and BuildRequire base.
I have another package: dep-11 which Requires dep1,base and BuildRequires dep1,base
I rebuild base in Plague and I would like a way to then automatically rebuild dep1 and dep2. And then rebuild dep-11.
Thanks for any help, John
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
On 03/28/2007 06:22 AM, Dan Williams wrote:
On Tue, 2007-03-27 at 19:56 -0700, John Villalovos wrote:
I have a question about Plague. Does Plague have the capability to handle dependencies where if you build one RPM that other RPMS depend on for their BuildRequires that you can then build all those RPMS and any other RPMS which maybe affected by building them?
ie, like debian's build system?
No, plague doesn't do that. It was a planned option but Koji is taking over for plague and I'm not sure if that's planned for Koji.
AFAIK, it's planned for koji. And don't blame me, but OpenSuSE's build system has this capability :-)
[ ... ]
-of
On Wed, 2007-03-28 at 08:58 +0200, Oliver Falk wrote:
On 03/28/2007 06:22 AM, Dan Williams wrote:
On Tue, 2007-03-27 at 19:56 -0700, John Villalovos wrote:
I have a question about Plague. Does Plague have the capability to handle dependencies where if you build one RPM that other RPMS depend on for their BuildRequires that you can then build all those RPMS and any other RPMS which maybe affected by building them?
ie, like debian's build system?
No, plague doesn't do that. It was a planned option but Koji is taking over for plague and I'm not sure if that's planned for Koji.
AFAIK, it's planned for koji. And don't blame me, but OpenSuSE's build system has this capability :-)
Yeah; it's nice to have. It's also a headache in some situations so it needs to be selectable.
Dan
[ ... ]
-of
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
On 03/28/2007 02:03 PM, Dan Williams wrote:
On Wed, 2007-03-28 at 08:58 +0200, Oliver Falk wrote:
On 03/28/2007 06:22 AM, Dan Williams wrote:
On Tue, 2007-03-27 at 19:56 -0700, John Villalovos wrote:
I have a question about Plague. Does Plague have the capability to handle dependencies where if you build one RPM that other RPMS depend on for their BuildRequires that you can then build all those RPMS and any other RPMS which maybe affected by building them?
ie, like debian's build system?
No, plague doesn't do that. It was a planned option but Koji is taking over for plague and I'm not sure if that's planned for Koji.
AFAIK, it's planned for koji. And don't blame me, but OpenSuSE's build system has this capability :-)
Yeah; it's nice to have. It's also a headache in some situations so it needs to be selectable.
I think, the bsys should raise up a list of deps that might need a rebuild; A webpage with checkboxes and a go button. :-) Eventuall a notification to the maintainer if build fails, and/or a bug#, whatever. But if you want autorebuilds in such a way, the system needs to know how to increase the release number and add a cl entry to the spec; Needs cvs commit rights and so on... Maybe nothing anyone wants to be automated... However, I'm not goin' to code this :-P
-of
On Thu, 29 Mar 2007 09:18:14 +0200, Oliver Falk wrote:
I think, the bsys should raise up a list of deps that might need a rebuild; A webpage with checkboxes and a go button. :-) Eventuall a notification to the maintainer if build fails, and/or a bug#, whatever. But if you want autorebuilds in such a way, the system needs to know how to increase the release number and add a cl entry to the spec; Needs cvs commit rights and so on... Maybe nothing anyone wants to be automated... However, I'm not goin' to code this :-P
And once it's made too easy to rebuild package sets like this, we will see many needless rebuilds in Fedora.
"Automatic rebuilds" in my opinion implies that there is a way to check automatically whether a rebuild is necessary. For instance, if a soname has changed and breaks the ABI. But the build system cannot know whether this is expected. 3rd party repositories which depend on our packages won't like such breakage and our attempts to work around it with automatic mass-rebuilds.
On 03/29/2007 10:50 AM, Michael Schwendt wrote:
On Thu, 29 Mar 2007 09:18:14 +0200, Oliver Falk wrote:
I think, the bsys should raise up a list of deps that might need a rebuild; A webpage with checkboxes and a go button. :-) Eventuall a notification to the maintainer if build fails, and/or a bug#, whatever. But if you want autorebuilds in such a way, the system needs to know how to increase the release number and add a cl entry to the spec; Needs cvs commit rights and so on... Maybe nothing anyone wants to be automated... However, I'm not goin' to code this :-P
And once it's made too easy to rebuild package sets like this, we will see many needless rebuilds in Fedora.
"Automatic rebuilds" in my opinion implies that there is a way to check automatically whether a rebuild is necessary. For instance, if a soname has changed and breaks the ABI. But the build system cannot know whether this is expected. 3rd party repositories which depend on our packages won't like such breakage and our attempts to work around it with automatic mass-rebuilds.
That's why I said, that the buildsystem should only do it semi-automatic; Only with human-intervention. :-)
-of
On Thursday 29 March 2007 04:50:40 Michael Schwendt wrote:
"Automatic rebuilds" in my opinion implies that there is a way to check automatically whether a rebuild is necessary. For instance, if a soname has changed and breaks the ABI. But the build system cannot know whether this is expected. 3rd party repositories which depend on our packages won't like such breakage and our attempts to work around it with automatic mass-rebuilds.
While I'm not in favor of fully automatic rebuilds, I am in favor of being able to do a repoclosure with your freshly built package against the repo that was used to BUILD said package and send alerts out to the person who built it and the person(s) who's packages might now have broken deps because of the build, as well as logging it to a webpage for a quick "hitlist" to keep track of. It would then be up to the maintainer(s) to either initiate rebuilds of the broken packages, or untag the new build as it would break too much.
On Thu, 2007-03-29 at 09:18 +0200, Oliver Falk wrote:
On 03/28/2007 02:03 PM, Dan Williams wrote:
On Wed, 2007-03-28 at 08:58 +0200, Oliver Falk wrote:
On 03/28/2007 06:22 AM, Dan Williams wrote:
On Tue, 2007-03-27 at 19:56 -0700, John Villalovos wrote:
I have a question about Plague. Does Plague have the capability to handle dependencies where if you build one RPM that other RPMS depend on for their BuildRequires that you can then build all those RPMS and any other RPMS which maybe affected by building them?
ie, like debian's build system?
No, plague doesn't do that. It was a planned option but Koji is taking over for plague and I'm not sure if that's planned for Koji.
AFAIK, it's planned for koji. And don't blame me, but OpenSuSE's build system has this capability :-)
Yeah; it's nice to have. It's also a headache in some situations so it needs to be selectable.
I think, the bsys should raise up a list of deps that might need a rebuild; A webpage with checkboxes and a go button. :-) Eventuall a
Two things I see with this:
1) I can rebuild any package without a maintainer's permission; That's going to be a problem in some cases.
2) We'd have to make 110% sure that a script that rebuilds the SRPMs and bumps the release correctly; often there are some packages that have problems with auto-bumped release. This could be solved through more stringent packaging guidelines.
Dan
notification to the maintainer if build fails, and/or a bug#, whatever. But if you want autorebuilds in such a way, the system needs to know how to increase the release number and add a cl entry to the spec; Needs cvs commit rights and so on... Maybe nothing anyone wants to be automated... However, I'm not goin' to code this :-P
-of
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
On 3/27/07, Dan Williams dcbw@redhat.com wrote:
On Tue, 2007-03-27 at 19:56 -0700, John Villalovos wrote:
I have a question about Plague. Does Plague have the capability to handle dependencies where if you build one RPM that other RPMS depend on for their BuildRequires that you can then build all those RPMS and any other RPMS which maybe affected by building them?
ie, like debian's build system?
No, plague doesn't do that. It was a planned option but Koji is taking over for plague and I'm not sure if that's planned for Koji.
Okay. Thanks for the info, not what I was hoping for, but thanks anyway :)
John
buildsys@lists.fedoraproject.org
-
Dan Williams -
Jesse Keating -
John Villalovos -
Michael Schwendt -
Oliver Falk