-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 James Ogley wrote:
in the moment, Rainer Lay hasn't much time, so i'll try to "fix" missing rpms for 10.0. mplayerplug-in is now online on packman. ;)
Cool, I've removed my packages now. Teamwork - it's a beautiful thing :)
Well, as I said/wrote again and again, it definately shows that we've been lacking a common
communication media.
Duplicate packages, recurring issues, maybe discussing over common style/guidelines for spec files,
etc...
At least that's the kind of things I hope we'll be able to talk about in some time (or maybe right now).
We definately need to work much closer together.
Most specifically, having duplicate packages is a big issue:
1) often they're not compatible and/or conflict:
different package name, different subpackaging, ...
2) issues for end-user who have several repositories in their inst sources
That's certainly the worst issue of them all, as we all want to give end-users a good experience and
easy of use, without what we wouldn't do all this packaging stuff ;)
3) duplicated work
Partly wasted time and effort for us packagers - and time sure is a valuable resource for all of us.
This also means that we should keep this list clear from any support question ("yast gives me an
error when I try to do a netinstall"-alikes).
Package-related bug reports.. hmm... why not.
Someone from SUSE mentioned that we could also use the openSUSE bugzilla to report issues about our
"community-made" packages. I don't remember who it was... Adrian, AJ, Christoph... ?
I would have a proposal: every time one of us makes a new package (not a new release, but start
packaging a project you didn't do before), send a mail on this list.
Like that, if someone else already packages/maintains it, we/they can discuss who maintains it, in
order to avoid duplication.
What do you guys think ? Feasible ? Too much overhead ?
Also, when we find out about cool RPM/spec tricks, gotchas, bugs, tools, scripts, whatever,
publicize it here.
This list can also be used to extend our know-how.
If some information is considered interesting or important enough to be "sticky", we can write it on
the opensuse wiki.
If noone is against it, I'll start doing so right now.
What about everyone maintaining a public repository introducing himself here ?
- - shortly
- - what repository do you maintain (suser-guru, usr-local-bin, packman, suser-gbv, ...)
- - what kind of software in your repo (anything, multimedia, server stuff, ...)
- - what SUSE versions do you build for
- - repo URLs/formats
- - email address, jabber ID, ...
Or maybe a page on the opensuse wiki ?
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\