On 06/29/2009 08:30 PM, Radu-Cristian FOTESCU wrote:
There is a reason for my repo (Odiecolon) to be what it is, and this has nothing to do
To a certain extent, you're right though. It were better to have had contacted EPEL,
this could have prevented some duplicate work, and it would have triggered the 64-bit
packages too (currently, I'm doing 32-bit only).
The problem is that my repo also includes packages that can't be part of EPEL for
various legal reasons. Even an "innocent" application such as Audacity has some
Welcome to the list. What I can see is your repo is packages roughly
classifiable into three different groups
* that can be part of EPEL - Deluge for example
* hacks - for various reasons that can't be in EPEL
* packages that are excluded from EPEL for legal reasons. RPM Fusion can
hold them however and is meant to be compatible with EPEL.
I suggest that you work with EPEL on packages that are cleanly in the
first category initially. The benefit is shared infrastructure (koji,
bodhi et all) that brings the packages you are interested in to more
architectures and a community for reviewing packages, get co-maintainers
to share the burden of maintenance which is useful in case you want to
work on other packages, fall sick, go on a vacation or just lose
interest. Sounds reasonable?