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)