Mailinglist Archive: opensuse-buildservice (314 mails)

< Previous Next >
[opensuse-buildservice] Re: Novell ID's for OSC Plugins
  • From: Rodrigo Moya <rodrigo@xxxxxxxxxx>
  • Date: Mon, 14 Jan 2008 14:26:57 +0100
  • Message-id: <1200317218.7168.27.camel@xxxxxxxxxxxxxx>
Hi

(sorry for the late answer)

On Wed, 2007-11-28 at 18:09 +0100, Dr. Peter Poeml wrote:
Hi,

thank you for your contributions!

On Wed, Nov 28, 2007 at 04:01:25PM +0100, Adrian Schröter wrote:
On Wednesday 28 November 2007 00:57:23 wrote JP Rosevear:
Hi Adrian, the two novell id's are "rodrigomoya" and "maw" for the osc
plugin developers.

both have been added to the openSUSE svn. Please tell, if you want to get
also
commit mails for the svn.

Checkout with

svn co https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice

Peter, can you define a directory where osc plugins should get submitted ?

I'd suggest either a new directory
trunk/buildservice/src/clientlib/python/osc-plugins
or a subdirectory
trunk/buildservice/src/clientlib/python/osc/osc/plugins or
trunk/buildservice/src/clientlib/python/osc/osc-plugins

IMO, one of the latter makes sense if the plugins should be
installed/packaged by default, together with osc. But then they could
just as well be implemented directly in osc, I guess.

But if the plugins are something which is not generally useful, or
should not be enabled by default, they should probably go into a
separate directory (the former directory I suggested).

ok, so here's the list of the plugins we already have, for discussion of
what should be included now and what should wait:

* osc-createspec: creates a .spec file from a set of templates. Right
now, we only have 'base', which creates a very basic .spec file, and
'gnome'. We should have similar templates for
KDE/java/python/whatever-based apps, etc

* osc-linkdereference: dereferences a linked package. I think this
mostly works ok, so should be mostly ready to add to the buildservice
SVN. Michael?

* osc-listpatches: lists patches for a set of packages. It displays
summaries of all packages and their patches. This is mostly ready for
inclusion.

* osc-patchlint: lint for patches, following the guidelines at:
http://en.opensuse.org/GNOME/Patches . These have been reviewed within
the opensuse-gnome team. Is this useful outside of GNOME? Could we have
these (or something similar) guidelines for the whole distro?

* osc-rewritespec: organize and rewrite parts of .spec files, like
ordering the Patch* lines. This is still incomplete.

* osc-deps: showd dependencies of a package. Incomplete

* osc-editchanges: like autobuild's 'vc'. Incomplete

* osc-mergefrom: merge 2 packages, not ready yet, although it might
almost be. Michael?

* osc-speclint: lint for .spec files. It's mostly working, so should be
mostly ready for inclusion.

what do you think?

--
Rodrigo Moya <rodrigo@xxxxxxxxxx>

---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
This Thread
Follow Ups