Mailinglist Archive: opensuse-packaging (186 mails)

< Previous Next >
Re: [opensuse-packaging] openSUSE vs Fedora packaging documentation
  • From: Michal Vyskocil <mvyskocil@xxxxxxx>
  • Date: Thu, 12 Feb 2009 08:47:15 +0100
  • Message-id: <200902120847.15960.mvyskocil@xxxxxxx>
On Wednesday 11 of February 2009 16:42:59 Andrew Wafaa wrote:
On Wed, 2009-02-11 at 16:24 +0100, Vincent Untz wrote:
Le mercredi 11 février 2009, à 15:51 +0100, Michal Vyskocil a écrit :
So main questions are:
- how could be Packaging/ maintained (eg. we would have a Docbook
original somewhere and convert it to wiki as SUSE packaging conventions
[2])? - how could we structure existing information to be more readable
and useful for community?
- what is missing, or unclear and needs to be improved?
(- and who will do this all ;-))

Can't we simply adopt the Fedora doc and make it a cross-distribution
(we might have some differences, but I'm sure we can drop some, and work
with Fedora people on a good way to highlight the differences)


Les gens heureux ne sont pas pressés.

Good idea.

I'm sure Fedora would be happy and willing to co-operate on this.
Having spoken to several people and been approached by several whilst at
FOSDEM about ways in which they can work with openSUSE and other
projects, they are keen to help in the cross pollination of information.

If Fedora would be interested, why not. I'm afraid that this would be better,
but rather impossible way. Stanislav Brabec told me about his effort on
unification of RPM macros used by various distributions, but it failed. It
failed on a simple reason - no one want to change his policy/macros/etc. I
CCing him, so he should be able provide more details about current state of
discussion on rpm-devel (or rpm-maint, I'm not sure) mailing list.

But if you know some interested guys from Fedora, I'm really interested on it
and I'll help if I can.

Best regards
Michal Vyskocil
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx

< Previous Next >