Hi, I thought about to create a svn repo for spec file templates. One for KDE, Gnome, perl, apache module or whatever. Is there some interest that we should create one or are you fine with the solution to have these in the wiki ? bye adrian -- Adrian Schroeter SuSE AG, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de
Adrian Schroeter schrieb:
Hi,
I thought about to create a svn repo for spec file templates. One for KDE, Gnome, perl, apache module or whatever.
Is there some interest that we should create one or are you fine with the solution to have these in the wiki ?
bye adrian
as there are already both the possibilities to put these in the wiki and also release the src.rpm, I think this is suitable for me, but these are only my 0.02 $. The bigger problem i see, is WHY some changes are made to exisiting spec files, as there is almost no documentation in these. But this is only my opinion, perhaps those more familiar with the process of packaging don't have this problem ;-) -rauch
On Wed, Sep 28, 2005 at 11:00:51AM +0200, Rauch Christian wrote:
Adrian Schroeter schrieb:
I thought about to create a svn repo for spec file templates. One for KDE, Gnome, perl, apache module or whatever.
Is there some interest that we should create one or are you fine with the solution to have these in the wiki ?
In my opinion a svn repository is better because the tools are just more mature for browsing history (to understand changes and so on) than using a browser and clicking through multiple history pages.
The bigger problem i see, is WHY some changes are made to exisiting spec files, as there is almost no documentation in these.
I can second that but that could be solved by the repository idea if you train people to write a useful change comment when they commit a change. Currently you often read in the changelog of many packages something like "removing foo bar" but nothing actually explains why this is removed from all packages. Most likely there was a choice based on a reason but it would be interesting to know this reason. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
On Wednesday 28 September 2005 11:29, Robert Schiele wrote:
On Wed, Sep 28, 2005 at 11:00:51AM +0200, Rauch Christian wrote:
Adrian Schroeter schrieb:
I thought about to create a svn repo for spec file templates. One for KDE, Gnome, perl, apache module or whatever.
Is there some interest that we should create one or are you fine with the solution to have these in the wiki ?
In my opinion a svn repository is better because the tools are just more mature for browsing history (to understand changes and so on) than using a browser and clicking through multiple history pages.
The bigger problem i see, is WHY some changes are made to exisiting spec files, as there is almost no documentation in these.
I can second that but that could be solved by the repository idea if you train people to write a useful change comment when they commit a change.
Currently you often read in the changelog of many packages something like "removing foo bar" but nothing actually explains why this is removed from all packages. Most likely there was a choice based on a reason but it would be interesting to know this reason.
okay, I will take care of creating an svn repo at novell forge (same logins as for Bugzilla and Wiki can be used). I hope, I can also motivate enough internal people to announce, maintain and document their spec file templates there :) bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de
Hi,
I thought about to create a svn repo for spec file templates. One for KDE, Gnome, perl, apache module or whatever.
Ain't it possible to provide an svn repo to store spec files? I would store in such a central place.
Is there some interest that we should create one or are you fine with the solution to have these in the wiki ?
bye adrian aging-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging-help@opensuse.org
For tmplates it is good enough (I think), but not for development. -- Richard Bos Without a home the journey is endless
I thought about to create a svn repo for spec file templates. One for KDE, Gnome, perl, apache module or whatever.
Sounds like a plan, would be useful for new packagers to get started building simple packages.
Ain't it possible to provide an svn repo to store spec files? I would store in such a central place.
Well, surely the build system once it comes onstream will serve this purpose, spec files would live there in order to be built from, as would sources and patches. -- James Ogley james@usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Make Poverty History: http://makepovertyhistory.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adrian Schroeter wrote:
Hi, Hallo Adrian
I thought about to create a svn repo for spec file templates. One for KDE, Gnome, perl, apache module or whatever.
Yes please, good idea.
Is there some interest that we should create one or are you fine with the solution to have these in the wiki ?
I second Richard and Robert: SVN repo is *much* better. I have a few templates and scripts to contribute, if people are interested. As I'm known to be one of the most prolific community packagers, I think they could prove to be useful for others ;) I'm going to document and rework them, then send them here on the list (or rather links to them) + some information. Sneak preview: http://linux01.gwdg.de/~pbleser/files/rpm/templates/ (best viewed/edited with emacs + rpm-mode) I also hacked a shell script that uses libxslt's xsltproc to retrieve project information from freshmeat.net project entries (e.g. http://freshmeat.net/projects-xml/gimp/gimp.xml) and format it into spec file syntax: http://linux01.gwdg.de/~pbleser/files/rpm/ffxml With the help of a few people at freenode's #emacs, I also wrote some elisp macro that calls that ffxml script and fills in the data at the right position in an existing spec file. If you use my templates, that elisp macro will grep for "%define _name ...", and use "..." as its default proposition for the freshmeat.net project name, which actually matches the name one would give to the RPM 90% of the time. Here's the stuff to include in your ~/.emacs: http://linux01.gwdg.de/~pbleser/files/rpm/ffxml-dot-emacs.el At least it almost always saves me from copy/pasting "Summary:", "%description" and "License:" from the website and/or README files. But, as said, I'm going to refactor the scripts, document them, etc... *if* there's any interest ;) cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser@skynet.be> <guru@unixtech.be> _\_v ===> FOSDEM 2006 -- February 2006 in Brussels <=== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFDOm+zr3NMWliFcXcRAv30AKCe7fuRYDqiCI30MlaZv0R3e9ZJfwCdGJnN pvucQwHmvSsnWf50RZQB2DQ= =K2w6 -----END PGP SIGNATURE-----
participants (6)
-
Adrian Schroeter -
James Ogley -
Pascal Bleser -
Rauch Christian -
Richard Bos -
Robert Schiele