[elrepo-devel] Contributions

[Nelson Marques]

No dia Sexta-feira, 13 de Janeiro de 2012, Phil Perryphil at elrepo.orgescreveu:

> On 13/01/12 00:29, Nelson Marques wrote:
> > Hi all,
> >
> > I'm a Enterprise Linux user and I do maintain a few a packages for
> personal
> > usage (and I'm also a casual client from a few kernel modules on ELREPO).
> > What would be the best way to submit a few packages?
> >
> > NM
> >
>
> Hi Nelson,
>
> Welcome to elrepo.
>
> There are a number of ways you can contribute depending upon your
> experience and how involved you wish to get:
>

Hi Phil,

Well, I'm far from being the supra-sumo packager and most of my experience
is actually around (open)SUSE Linux where I maintain a few packages and
projects, though more oriented to the GNOME Desktop Environment.

I don't have extensive experience for Fedora/RHEL as a packager (though I
do work with it for the past 12 years), but I think I can manage :)


>
> 1. You could put in an RFE request at elrepo.org/bugs and ask one of the
> existing packagers/developers to pick up the package.
>
> 2. You could develop/maintain the package yourself and contribute it via
> our github repository and have one of the developers build and sign it
> for you and push it into the repo. See here:
>
> https://github.com/elrepo/packages/
>
> 3. Finally you could become an elrepo developer, and build/maintain the
> package yourself on the elrepo build systems, then only requiring an
> elrepo admin to sign and push the finished packages.
>
> All of which hopefully provides enough options to suit most needs.
>

As long as reviews/commits are done in less time than EPEL, that's cool
with me.


>
> Please keep in mind elrepo is primarily a repository for packages that
> provide improved hardware support for RHEL. These will mostly be kernel
> driver (kmod) packages. We only provide non-kmod packages where there is
> a very specific need such as an updated lm_sensors package required to
> support some hwmon kmod drivers, or some Xorg drivers in reqular RPM
> packages. All other packages would be better maintained in other
> dedicated repositories such as rpmforge (repoforge) or EPEL.
>


Another question, for example, I would like to submit an updated package of
DAHDI (system space and userland) which is somehow more complete than the
current that you offer and has been properly tested. As some might be
aware, this kernel module is used by Asterisk (either to load hardware
drivers or a dummy/pseudo software driver). Your current package has a few
nasty flaws which I can point:

 * It doesn't provide the udev rules which has a dreadful impact on the
system: devices are created owned by root:root and using 0600 permissions,
which makes it rather unusable with Asterisk. It should be owned by user
'asterisk' and group 'asterisk' and created with permissions 0660 (upstream
default). If people want to use it for the pseudo driver, there's a huge
change it's not gonna work 'out of the box' without some tinkering (ex:
hack the dahdi-tools sysv init scripts to change the permissions). If you
use real hardware, you don't ship with the firmware, leading to another
problem.

Would an updated (2.4.1.2 for kmod and 2.4.1 for tools) package which
provides a more complete set of options and which is actually according to
Red Hat packaging rules (the current one does't offer the dahdi-kmod-common
which is mandatory according to Fedora EPEL documentation) be of any
interest?

I am ready to submit at least this package soon. I could submit to EPEL,
but EPEL reviews take way too much time and I have a load of packages
pending there.

NM



>
> Hope that helps.
>
> Regards,
>
> Phil
> _______________________________________________
> elrepo-devel mailing list
> elrepo-devel at lists.elrepo.org <javascript:;>
> http://lists.elrepo.org/mailman/listinfo/elrepo-devel
>


-- 
Nelson Marques

/* http://www.marques.so
  nmo.marques at gmail.com */
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elrepo.org/pipermail/elrepo-devel/attachments/20120113/618d476d/attachment.html>