incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Burrell Donkin <>
Subject Re: Getting Apache [project] included in Linux distributions
Date Sat, 11 Apr 2009 19:39:43 GMT
On Fri, Apr 10, 2009 at 11:20 AM, Hans de Goede <> wrote:
> On 04/09/2009 02:13 PM, Robert Burrell Donkin wrote:
>> On Thu, Apr 9, 2009 at 10:48 AM, Chris Chabot<>  wrote:
>>> Ps, Hans De Goede has a bit more experience with several distro's then me
>>> and offered to help out too, i've added him to the CC list.
>> great :-)
> Hi all,
> I hope non subscriber posts to work. Short
> self intro: I've been a Free software developer for circa 10 years and
> the last 5 years I've been doing Fedora packaging (amongst other things).
> As my email address shows I'm currently working for RedHat
> (for 7 months now).
> <stddisclaimer.h>
> Everything I contribute to this discussion is my personal input,
> I'm not talking on behalf of RedHat nor of the Fedora project.
> </stddisclaimer.h>

great :-)

> As Fedora packager I'm in contact with packagers from various other
> distributions, but I'm in no way an expert on packaging for other distros.
> The best place to contact people involved in packaging with other distros
> is probably the distro neutral packaging discussion list at

volunteers to say hello over there?

> <snip>
>> [general]
>> picking up with the advice from chris, i suppose apache projects need
>> to actively engage with the distros, rather than just expecting it to
>> happen or demanding that someone else does the work. so - i guess -
>> that the first step should be to find volunteers from the apache
>> community (who need not be developers) who are interested in working
>> with the linux distros. as a second step, take time to understand the
>> distro community (and whether there might already be some people there
>> who are interested), to understand the rules of the community and to
>> work out what - if anything - is already happening in this area.
> Ack,
> There are 2 ways to get packages for a piece of Free software into a
> community distro like Fedora / Debian / Ubuntu, 1 is to find someone
> within the apache project who will do the packaging and have him get
> into contact with the distribution. More open distro's usually have
> quite extensive documents about both packaging guidelines as well as
> the process of becoming a packager.
> The second method is to find people within the distro who might be
> willing to do the work for you. In my own experience it is always
> very nice to have an upstream which actively collaborates in packaging,
> so if you advertise you are looking for packagers some people might bite.
> you could try to send a mail to fedora-devel-list:
> (subscribtion mandatory for sending)

makes sense :-)

> Explaining which apache projects you would like to see packaged, with
> a short description of the package, potential users, and basically
> some advertising as to why it should be part of Fedora. Your luck here
> will probably very wildly, but you might get lucky. I'm sure other
> distros have similar mailinglists where you could send such a request.


we can probably start pulling together some documentation on this and
starting to try to discover some contacts

>> what about dependencies?
> I assume you mean libraries / other software on which the project
> you want to package depends. Chances are good most are already packaged
> if not you will have to package them too.
>> [fedora]
>> AFAICT chris has done a good job on this: is there anything else to add?
> Not really :)

cool :-)

>> [redhat]
>> is the best way into redhat through fedora?
> I assume you mean RHEL here,

(i was fishing :-)

> getting into RHEL itself depends upon customer
> demand (as once something is in RedHat obliges itself to support it),
> there is not much you can do there.
> However under the Fedora project there also is the EPEL project for RHEL
> add-on packages using the same procedures as for regular Fedora packages.
> Once you have Fedora packages getting packages in to EPEL requires little
> effort (assuming the deps are already in EPEL), see:


thanks for the help

- robert

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message