[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: packaging sfxr

2008/11/17 Hans de Goede <j.w.r.degoede@hhs.nl>:

> I think you're thinking too much Debian-ess here, Debian (AFAIK) has a
> rather weird setup with different groups using different VCS's, quite a few
> other distro's have a pretty cleans setup with one VCS neatly and orderly
> containing all patches and other packaging files, see for example:
> http://cvs.fedoraproject.org/viewvc/devel/xawtv
> http://cvs.mandriva.com/cgi-bin/viewvc.cgi/SPECS/SDL/
> http://svn.rpmforge.net/svn/trunk/rpms/allegro/

Hey, I think Debian-like the same way that you probably think Fedora-like :P

I understand that you are involved in Fedora because you think it's
the best distro, the same reason I am in Debian ;)

I was also thinking about Gentoo and, in fact, all the distros that
are community-driven and not have one company behind. In any case, I
wouldn't want to tell any other distro how they should organize
themselves, so I think it would be positive to define the requisites
we expect from everyone involved and not assume anything about their
inner organization. That way we let the door open to everyone who
wants to join, independently of how they manage to organize

> So those are easy to "harvest", some make it somewhat harder, for example:
> http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/SPECS/
> Contains all spec files for pld-linux, then one needs to go to:
> http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/SOURCES/
> To find the actual patches referenced from those spec files.
> Others are even harder, for some reason opensuse seems to disappoint me
> about its openness each time, I couldn't find anything resembling a VCS on
> their site, I also love their how to contribute page:
> "The most obvious way, for programmers, to participate in the development of
> openSUSE is to post a patch as a suggested solution to an existing bug in
> Bugzilla. Each package has a maintainer, who will contact you to discuss
> your proposed solution. You may want to join one of our  development mailing
> lists before you start coding in order to discuss your plans and coordinate
> with other developers."
> So it looks like there is no way to get opensuse patches other then
> unpacking the SRPMS they provide.

The should have to find a way to make them available if they want to
join us, I guess. In any case it wouldn't hurt to contact them.

>> Maybe we should try to contact other
>> distros in this early stage to see if they want to become involved in
>> its design?
> Yes, I think that would be a good idea, go ahead. I wouldn't count on us
> succeeding in defining one way to get to the actual per distro patches
> though, I think we need to have a modular collection engine, which has per
> distro plugins.



Reply to: