I'll fix up my script a bit on the weekend and publish it here... hope this won't be to late for you.

Thank you Dominique, The project for which I am interested has already a script that does exactly what you have suggested via a third machine with a cron job. (http://www.projectaten.org/) As a matter of principle, I am interested if the same output can be achieved avoiding the third machine and using the cmake package generation capabilities to get the packages for various distributions. Alin -- ______________________________________________________________________ "...if the universities will not study useless subjects, who will?" G. F. Fitzgerald, Nature, 45/46, 392 (1892) ______________________________________________________________________ Mr. Alin M. ELENA Atomistic Simulation Centre School of Mathematics and Physics Queen's University Belfast Office: +44 (0)28 9097 1428 Fax: +44 (0)28 9097 5359 http://titus.phy.qub.ac.uk/group/Alin/ alin.elena@yahoo.co.uk alin.elena@qub.ac.uk ______________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On 2008-09-19 12:46:39 -0600, Boyd Lynn Gerber wrote:

On Fri, 19 Sep 2008, Dominique Leuenberger wrote:

...

On Fri, 2008-09-19 at 16:46 +0100, Alin M Elena wrote:

...

Hi Dominique,

...

The best would be to have the svn checkout on one of your own workstations, build up a tarball, commit it using osc and have new packages come out at the end.

...

This can be automated using scripts / cron. (I have a similiar script for one of my packages, getting packages from sv, updating the spec file with the release number, equal to the svn rev)

This is exactly what I want to avoid. The existence of the third actor.

Alin

I'll fix up my script a bit on the weekend and publish it here... hope this won't be to late for you.

I think it would be great if/when you do this that we could get it. Maybe we could get a SUSE/Novell, repo for such things. A community/contrib location for OBS and packaging.

Hmm openSUSE:Tools might be appropriate for such things but instead of publishing various scripts which are able to check out sources from svn, cvs, git etc. we should integrate such a feature directly into the buildservice (IMHO). In the past a lot of people requested such a feature but as the main obs devs are busy with other more important things this might be a nice task for the community:) - I would really like to help to integrate such a feature into the obs (are there any other volunteers?). Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Marcus Hüwe writes:

Hmm openSUSE:Tools might be appropriate for such things but instead of publishing various scripts which are able to check out sources from svn, cvs, git etc. we should integrate such a feature directly into the buildservice (IMHO). In the past a lot of people requested such a feature but as the main obs devs are busy with other more important things this might be a nice task for the community:) - I would really like to help to integrate such a feature into the obs (are there any other volunteers?).

Not sure what you mean: obs polling for new versions? or hopefully $outside pushing new versions into obs when they are available? Each svn, cvs and AFAICT even git have hook mechanism to do something if specific checkins happen in the repo. I'd suggest to rather invest into a clean and simple way to push new versions into the obs from such hooks. These hooks can either run on the repo host site or they can run on any dedicated client from e.g. a procmail rule, reacting on mail notifications from svn, cvs or git. I've started such a push-script for the obs itself, but I'm unbiassed wether to go with that or to create another one: https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/dist/distribute S. -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On 2008-09-22 10:10:15 +0200, Susanne Oberhauser wrote:

Marcus Hüwe writes:

...

Hmm openSUSE:Tools might be appropriate for such things but instead of publishing various scripts which are able to check out sources from svn, cvs, git etc. we should integrate such a feature directly into the buildservice (IMHO). In the past a lot of people requested such a feature but as the main obs devs are busy with other more important things this might be a nice task for the community:) - I would really like to help to integrate such a feature into the obs (are there any other volunteers?).

Not sure what you mean:

obs polling for new versions?

or hopefully $outside pushing new versions into obs when they are available?

I don't mean that the obs should poll for new versions every n minutes. For instance if you package svn snapshots the current procedure is the following: - checkout the source code - create a tarball - upload this tarball to the obs So IMHO it would be nice to add an apicall to tell the obs to checkout the source code and to create the tarball etc. The advantage is that the packager doesn't have to upload the tarball (this may take some time if you have big projects..).

Each svn, cvs and AFAICT even git have hook mechanism to do something if specific checkins happen in the repo.

I'd suggest to rather invest into a clean and simple way to push new versions into the obs from such hooks.

These hooks can either run on the repo host site or they can run on any dedicated client from e.g. a procmail rule, reacting on mail notifications from svn, cvs or git.

Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org