Mailinglist Archive: opensuse-buildservice (349 mails)

< Previous Next >
Re: [opensuse-buildservice] osc rdiff (was Re: Novell ID's for OSC Plugins)
  • From: "Dr. Peter Poeml" <poeml@xxxxxxx>
  • Date: Thu, 29 Nov 2007 17:21:43 +0100
  • Message-id: <20071129162143.GX30003@xxxxxxx>
On Thu, Nov 29, 2007 at 01:33:47PM +0100, Adrian Schröter wrote:
On Thursday 29 November 2007 13:24:12 wrote Dr. Peter Poeml:
So you can do this via the api:

curl -X POST -H "Content-Length: 0" -0 -n \

"https://api.opensuse.org/source/openSUSE:Tools/build?cmd=diff&oproject=o
penSUSE:Factory"

An osc equivalent of this command would be
osc req -m POST
"/source/openSUSE:Tools/build?cmd=diff&oproject=openSUSE:Factory"

sure, but this is not really intuitive to use ;)

I posted this just because it is *easier* to use than the curl command,
IMO.

osc has no support for requesting a diff between *two* arbitrary
packages. So far, "osc diff" can create diffs of different revisions of
*one* package.

It should be possible to implement an osc subcommand for this with a few
lines.

To integrate the functionality into the existing osc diff subcommand
might be a little more work (it needs some consideration to come up with
a sane user interface).

osc diff is just for a checked out package, right ?

Yes.

an equivalent for cvs rdiff would work without any checked out sources, just

osc rdiff <TO_PROJECT> <TO_PACKAGE> [--package <FROM_PACKAGE>] [--project
<FROM_PROJECT>]

It'd also need options for revision and orevision.

How about

osc rdiff [-rN[:M]] [[--oldprj OLD_PROJECT] --oldpkg OLD_PACKAGE]] NEW_PROJECT
NEW_PACKAGE

One should note that the result is a "pretty diff", which goes into tar
balls and is handy for reviews -- not a normal diff which yields an
appliable patch.

hm, maybe even default to "--project openSUSE:Factory" if no argument is
given ...

Maybe a good idea...

Peter
--
"WARNING: This bug is visible to non-employees. Please be respectful!"

SUSE LINUX Products GmbH
Research & Development
< Previous Next >
Follow Ups