[opensuse-buildservice] osc missing features
Hello, during the usage of osc in last time I found 2 features missing: a) When I'm e.g. in my home project I can't use osc ci -"mxxx" to checkin all the changes in the subprojects. Why? b) osc build cannot be used to simulate BuildService builds: I would wish following option - When I'm in a package, the third argument with the specfile can be omitted and the build builds the package. Including following: 1) Getting all relevant files needed for this including the _link files 2) Applying patches like on buildservice 3) Build using the locally modified working copy c) Passing a package name as third argument should have same effect as b). 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
Hi, On 2007-08-17 09:46:02 +0200, Dirk Stoecker wrote:
Hello,
during the usage of osc in last time I found 2 features missing:
a) When I'm e.g. in my home project I can't use osc ci -"mxxx" to checkin all the changes in the subprojects. Why?
A subproject and a project are 2 independent things. The subproject isn't related to "main" project and vice versa.
b) osc build cannot be used to simulate BuildService builds: I would wish following option - When I'm in a package, the third argument with the specfile can be omitted and the build builds the package. Including following: 1) Getting all relevant files needed for this including the _link files 2) Applying patches like on buildservice 3) Build using the locally modified working copy
Support for building linked packages is planned but it still needs to be discussed where to patch the sources (either this happens in the buildservice or in build but not in osc). I don't know the current status of this discussion.
c) Passing a package name as third argument should have same effect as b).
Hmm what's the advantage of this? Your $PWD is the package dir and you pass the package name as the third argument instead of the spec file (or is $PWD your project dir)? Sorry I don't get this point:/ Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 17 August 2007 15:12:22 wrote Marcus Hüwe:
On 2007-08-17 09:46:02 +0200, Dirk Stoecker wrote: ..
b) osc build cannot be used to simulate BuildService builds: I would wish following option - When I'm in a package, the third argument with the specfile can be omitted and the build builds the package. Including following: 1) Getting all relevant files needed for this including the _link files 2) Applying patches like on buildservice 3) Build using the locally modified working copy
Support for building linked packages is planned but it still needs to be discussed where to patch the sources (either this happens in the buildservice or in build but not in osc). I don't know the current status of this discussion.
the backend source server can already merge the sources. However, it may make sense to do it in the cli in your case, because it would make it easier to create modified source links and to maintain the patches there ? bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2007-08-17 17:11:37 +0200, Adrian Schröter wrote:
On Friday 17 August 2007 15:12:22 wrote Marcus Hüwe:
On 2007-08-17 09:46:02 +0200, Dirk Stoecker wrote: ..
b) osc build cannot be used to simulate BuildService builds: I would wish following option - When I'm in a package, the third argument with the specfile can be omitted and the build builds the package. Including following: 1) Getting all relevant files needed for this including the _link files 2) Applying patches like on buildservice 3) Build using the locally modified working copy
Support for building linked packages is planned but it still needs to be discussed where to patch the sources (either this happens in the buildservice or in build but not in osc). I don't know the current status of this discussion.
the backend source server can already merge the sources. However, it may make sense to do it in the cli in your case, because it would make it easier to create modified source links and to maintain the patches there ?
the plan is that michael extracts the needed code and puts it into the build.rpm package. so osc can just call the same script as the backend would do at that point. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Aug 17, 07 17:29:12 +0200, Marcus Rueckert wrote:
On 2007-08-17 17:11:37 +0200, Adrian Schröter wrote:
On Friday 17 August 2007 15:12:22 wrote Marcus Hüwe:
On 2007-08-17 09:46:02 +0200, Dirk Stoecker wrote: ..
b) osc build cannot be used to simulate BuildService builds: I would wish following option - When I'm in a package, the third argument with the specfile can be omitted and the build builds the package. Including following: 1) Getting all relevant files needed for this including the _link files
Please find attached my osc_expand_link tool. I don't know if equivalent code exists in osc or build.rpm It did not, when I wrote the tool. cheers, Jw.
2) Applying patches like on buildservice 3) Build using the locally modified working copy
Support for building linked packages is planned but it still needs to be discussed where to patch the sources (either this happens in the buildservice or in build but not in osc). I don't know the current status of this discussion.
the backend source server can already merge the sources. However, it may make sense to do it in the cli in your case, because it would make it easier to create modified source links and to maintain the patches there ?
the plan is that michael extracts the needed code and puts it into the build.rpm package. so osc can just call the same script as the backend would do at that point.
darix
-- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de wide open suse_/ _---|____________\/ \ | 0911 74053-508 (tm)__/ (____/ /\ (/) | __________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) "This bug is visible to non-employees. Please be respectful." (bugzilla)
On Fri, 17 Aug 2007, Marcus Hüwe wrote:
during the usage of osc in last time I found 2 features missing:
a) When I'm e.g. in my home project I can't use osc ci -"mxxx" to checkin all the changes in the subprojects. Why?
A subproject and a project are 2 independent things. The subproject isn't related to "main" project and vice versa.
Ok. My error. I mean the packages. osc update and osc status and all the others work. Why not osc commit?
b) osc build cannot be used to simulate BuildService builds: I would wish following option - When I'm in a package, the third argument with the specfile can be omitted and the build builds the package. Including following: 1) Getting all relevant files needed for this including the _link files 2) Applying patches like on buildservice 3) Build using the locally modified working copy
Support for building linked packages is planned but it still needs to be discussed where to patch the sources (either this happens in the buildservice or in build but not in osc). I don't know the current status of this discussion.
c) Passing a package name as third argument should have same effect as b).
Hmm what's the advantage of this? Your $PWD is the package dir and you pass the package name as the third argument instead of the spec file (or is $PWD your project dir)? Sorry I don't get this point:/
E.G. To build a buildservice package from scratch without checking it out first. If all the download code for links and related stuff exists, it should be not problem to do this as well :-) Ciao -- http://www.dstoecker.eu/ (PGP key available)
On Mon, Aug 20, 2007 at 10:25:39AM +0200, Dirk Stoecker wrote:
On Fri, 17 Aug 2007, Marcus Hüwe wrote:
during the usage of osc in last time I found 2 features missing:
a) When I'm e.g. in my home project I can't use osc ci -"mxxx" to checkin all the changes in the subprojects. Why?
A subproject and a project are 2 independent things. The subproject isn't related to "main" project and vice versa.
Ok. My error. I mean the packages. osc update and osc status and all the others work. Why not osc commit?
Maybe I don't understand what you mean, but this works for me: poeml@batavia510 ~/bs/home:poeml % echo >> test/bar1 poeml@batavia510 ~/bs/home:poeml % echo >> test5/asdf poeml@batavia510 ~/bs/home:poeml % osc st test/bar1 test5/asdf M test/bar1 M test5/asdf poeml@batavia510 ~/bs/home:poeml % osc ci -m "fasel" test test5 Sending bar1 Transmitting file data . Committed revision 999. Sending asdf Transmitting file data . Committed revision 117.
b) osc build cannot be used to simulate BuildService builds: I would wish following option - When I'm in a package, the third argument with the specfile can be omitted and the build builds the package. Including following: 1) Getting all relevant files needed for this including the _link files 2) Applying patches like on buildservice 3) Build using the locally modified working copy
Support for building linked packages is planned but it still needs to be discussed where to patch the sources (either this happens in the buildservice or in build but not in osc). I don't know the current status of this discussion.
The status which was documented here: http://lists.opensuse.org/opensuse-buildservice/2007-07/msg00043.html still reflects the latest state of the discussion on local build of linked packages, as far as I know. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
On Mon, 20 Aug 2007, Dr. Peter Poeml wrote:
On Mon, Aug 20, 2007 at 10:25:39AM +0200, Dirk Stoecker wrote:
On Fri, 17 Aug 2007, Marcus Hüwe wrote:
during the usage of osc in last time I found 2 features missing:
a) When I'm e.g. in my home project I can't use osc ci -"mxxx" to checkin all the changes in the subprojects. Why?
A subproject and a project are 2 independent things. The subproject isn't related to "main" project and vice versa.
Ok. My error. I mean the packages. osc update and osc status and all the others work. Why not osc commit?
Maybe I don't understand what you mean, but this works for me:
poeml@batavia510 ~/bs/home:poeml % echo >> test/bar1 poeml@batavia510 ~/bs/home:poeml % echo >> test5/asdf poeml@batavia510 ~/bs/home:poeml % osc st test/bar1 test5/asdf M test/bar1 M test5/asdf poeml@batavia510 ~/bs/home:poeml % osc ci -m "fasel" test test5 Sending bar1 Transmitting file data . Committed revision 999. Sending asdf Transmitting file data . Committed revision 117.
Assuming only changes in test and test5 the following commands should be equal: "osc status test test5" works "osc diff test test5" works "osc ci test test5" works "osc status" works "osc diff" does not work "osc ci" does not work "osc log" does not work (should show log for all packages) "osc log test test5" does not work "osc log" does not work Comparing the behaviour to cvs and svn I would expect all of the above commands to work. Possibly with "osc ci" a security request can be added to ask if it is really meant to checkin everything :-) Ciao -- http://www.dstoecker.eu/ (PGP key available)
participants (6)
-
Adrian Schröter -
Dirk Stoecker -
Dr. Peter Poeml -
Juergen Weigert -
Marcus Hüwe -
Marcus Rueckert