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:
- Getting all relevant files needed for this including the _link files
- Applying patches like on buildservice
- 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.