Mailinglist Archive: opensuse-buildservice (354 mails)

< Previous Next >
[opensuse-buildservice] Upstream integration
  • From: "Rafal Kwasny" <rafal.kwasny@xxxxxxxxx>
  • Date: Tue, 13 Feb 2007 09:40:39 +0100
  • Message-id: <801d89860702130040l67963374pf164de49a6a00d6f@xxxxxxxxxxxxxx>
Hi,
during summer of code I wrote part of upstream integration for the BS
it works by parsing _upstream file located in package directory

_upstream looks like this:

<upstream>
<source>
<file archive='tar' compress='gzip'>mytarball.tgz</file>
<svn>
<destdir>common</destdir>
<url>https://server/path</url>
</svn>
<exclude>somefile</exclude>
<exclude>anotherfile</exclude>
</source>
<source>
<file archive='tar' compress='gzip'>myothertarball.tgz</file>
<cvs>
<cvsroot>cvs.example.com</cvsroot>
<path>abc/def</path>
<user>someuser</user>
<password>pass</password>
<branch>REL_1_0</branch>
</cvs>
</source>
</upstream>


The question is - where to integrate this?
I propose adding path in api, something like
GET /source/<project>/<package>/make_upstream
or may be better to
POST /source/<project>/<package>?cmd=fetchUpstreamSource

or make a new controller

GET /upstream/<project>/<package>/fetch

What you think of it?

--
Regards
^^MAg^^ mailto:/jid: mag@xxxxxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >