[opensuse-buildservice] osc package-tracking branch
Hi, we need your input with this one :-) Marcus has been developing the so-called package tracking branch for osc since quite a while. We both believe it would be good to merge it back into trunk. For that, it would be very helpful to know from you: * if anyone has used that branch lately * what you think about the functionality What does it do? In short, it "watches" a project checkout for changes, and keeps track of the contained packages (hence the name). Thus, - new directories that you create there, can be osc add'ed and checked in, without the need to create them first - adds a command mkpac which achieves the same - possibly other things, that I don't have on my radar ;) Marcus, maybe you can add some explanations about the functionality. You are the master :-) The functionality is _optional_. It needs to be switched on with do_package_tracking = 1 in .oscrc. If that is _not_ set, osc will behave just the same as it die before. Myself, I have been using the branch since many months, and it basically works fine for me. I used it with do_package_tracking = 1 since the beginning. So, I would like to hear from people who used it -- also people who didn't set do_package_tracking = 1 in their config but used the branch. (Darix?) Thanks, Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
On Wed, Mar 05, 2008 at 10:13:22PM +0100, Dr. Peter Poeml wrote:
Hi,
we need your input with this one :-)
And here are the instructions. (I didn't want to write a monster mail which nobody can grok anymore.) The "normal" osc lives here: https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/clientlib/p... The branch in question is here: https://forgesvn1.novell.com/svn/opensuse/branches/buildservice/osc-package-... Using it directly from svn is very simple: svn co https://forgesvn1.novell.com/svn/opensuse/branches/buildservice/osc-package-... ln -s `pwd`/osc-package-tracking/osc-wrapper.py ~/bin/osc (or you link it somewhere else.) That osc should work exactly like trunk. Let us know if not, please! And to use it in package-tracking mode, set do_package_tracking = 1 in .oscrc's [general] section. Feedback for that one is just as interesting. Thanks! Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Hi, On 2008-03-05 22:13:22 +0100, Dr. Peter Poeml wrote:
Hi,
we need your input with this one :-)
Marcus has been developing the so-called package tracking branch for osc since quite a while. We both believe it would be good to merge it back into trunk.
For that, it would be very helpful to know from you:
* if anyone has used that branch lately
* what you think about the functionality
What does it do?
In short, it "watches" a project checkout for changes, and keeps track of the contained packages (hence the name). Thus,
- new directories that you create there, can be osc add'ed and checked in, without the need to create them first - adds a command mkpac which achieves the same - possibly other things, that I don't have on my radar ;)
Basically the aim of this feature is that you can create/delete etc. packages in an easy way. Here's a small demo of what you can do with it: # checkout a new project with existing packages: marcus@linux:~> osc ls home:Marcus_H:demo foo test marcus@linux:~> osc co home:Marcus_H:demo A home:Marcus_H:demo A home:Marcus_H:demo/foo A home:Marcus_H:demo/foo/foo.spec A home:Marcus_H:demo/test A home:Marcus_H:demo/test/test.spec # add a new package+files to this project: marcus@linux:~/home:Marcus_H:demo> osc mkpac bar A bar marcus@linux:~/home:Marcus_H:demo> touch bar/{file1,file2,file3} marcus@linux:~/home:Marcus_H:demo> osc add bar/* A bar/file1 A bar/file2 A bar/file3 # remove an existing package+files from the project: marcus@linux:~/home:Marcus_H:demo> osc rm foo/ D foo/foo.spec D foo # print out the status of all packages+files: marcus@linux:~/home:Marcus_H:demo> echo "# modified" >> test/test.spec marcus@linux:~/home:Marcus_H:demo> osc st D foo D foo/foo.spec M test/test.spec A bar A bar/file1 A bar/file2 A bar/file3 # finally commit all changes to the BuildService: marcus@linux:~/home:Marcus_H:demo> osc ci Deleting foo Sending test/test.spec Transmitting file data . Committed revision 2. Sending meta data... Done. Sending bar Sending bar/file1 Sending bar/file2 Sending bar/file3 Transmitting file data ... Committed revision 1. # the package "foo" was removed and "bar" was added: marcus@linux:~/home:Marcus_H:demo> osc ls home:Marcus_H:demo bar test I hope this gives a basic overview about this functionality. It probably comes in handy for the people who want to control their packages in a svn-like way. If you have questions, remarks etc. please let us know:) Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Le jeudi 06 mars 2008 à 13:59 +0100, Marcus Hüwe a écrit :
I hope this gives a basic overview about this functionality. It probably comes in handy for the people who want to control their packages in a svn-like way.
If you have questions, remarks etc. please let us know:)
Looks really cool :-) Thanks for the overview! Vincent -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Mar 05, 2008 at 10:13:22PM +0100, Dr. Peter Poeml wrote:
we need your input with this one :-)
Marcus has been developing the so-called package tracking branch for osc since quite a while. We both believe it would be good to merge it back into trunk.
We didn't get a much feedback on this, unfortunately. However it blocks the development somehow. Thus, I suggest that we do the merge and release it into the wild. In case something breaks, we can still roll the change back. I don't expect it, and the risk seems small. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
On Mon, Mar 10, 2008 at 01:08:36PM +0100, Dr. Peter Poeml wrote:
On Wed, Mar 05, 2008 at 10:13:22PM +0100, Dr. Peter Poeml wrote:
we need your input with this one :-)
Marcus has been developing the so-called package tracking branch for osc since quite a while. We both believe it would be good to merge it back into trunk.
We didn't get a much feedback on this, unfortunately. However it blocks the development somehow. Thus, I suggest that we do the merge and release it into the wild. In case something breaks, we can still roll the change back. I don't expect it, and the risk seems small.
Merged. Don't forget to update your working copies. Packages are also building. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
participants (3)
-
Dr. Peter Poeml -
Marcus Hüwe -
Vincent Untz