I won't, at least for now, maintain the packages I maintain in EPEL-5 in
EPEL-6. I have added a nobranch file in all of them. If you want to take up
the package, you can. It is still unclear to me how to practically ensure
that you become the EPEL-6 branch owner, instead of me, though. Hopefully
this will be sorted out.
If you want to maintain the EL-5 (or even EL-4) branch too, don't
hesitate, the less package I maintain the better I am.
I think that wdm should not be maintained in EL-6 anyway, since upstream
is dead and there is no ConsoleKit integration.
For the dap-* packages it maybe worth waiting for a stabilisation of
the ABI, and maybe integration with bes and packaging of olfs to have a
working hyrax server before branching. My guess is that there are no
users of these packages anyway. Also maybe the opendap implementantion
in netcdf itself could be used instead of libdap/libnc-dap.
--
Pat
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
05-01-2010, 02:51 PM
Patrice Dumas
my EPEL-6 packages up for takers
Hello,
I won't, at least for now, maintain the packages I maintain in EPEL-5 in
EPEL-6. I have added a nobranch file in all of them. If you want to take up
the package, you can. It is still unclear to me how to practically ensure
that you become the EPEL-6 branch owner, instead of me, though. Hopefully
this will be sorted out.
If you want to maintain the EL-5 (or even EL-4) branch too, don't
hesitate, the less package I maintain the better I am.
I think that wdm should not be maintained in EL-6 anyway, since upstream
is dead and there is no ConsoleKit integration.
For the dap-* packages it maybe worth waiting for a stabilisation of
the ABI, and maybe integration with bes and packaging of olfs to have a
working hyrax server before branching. My guess is that there are no
users of these packages anyway. Also maybe the opendap implementantion
in netcdf itself could be used instead of libdap/libnc-dap.
my EPEL-6 packages up for takers
