Hi, earlier I asked (well, I don't know if it made it to the list... I
It did, after 10 hours.
[]
Anyway, let me know what I need to do to begin helping!
I guess the standard procedure would be to start by submitting revised versions of these packages to the package submission tracker (possibly accompanied by a gentle nudging on fink-devel if reactions on the tracker are too slow). This concerns existing packages that you want to maintain as well as new packages. In this way, people can look whether your packages are working and also help you with the mistakes you will inevitably make at the beginning. You see, it first has to be established whether having you as a maintainer is better than having no maintainer ;-)
You probably should also look at the cvs logs to see whether these packages are really unmaintained. Some of them might in fact be collectively maintained or have de-facto maintainers who, for whatever reason, don't show up in the Maintainer field.
Also, as you have seen in the case of Justin's packages, the Fink package database is not very intelligent when it comes to packages where several versions have different maintainers. Sometimes only older versions are unmaintained.
I only have access to my powerbook running Panther (10.3.3 currently). I don't know if that is going to be a problem for maintaining packages.
No principal problem here (except you can't take over maintainership of Justin's abandoned 10.2-gcc3.3 packages, which is a pity. Someone should).
In any case, I am sure everybody here welcomes you and your offer.
-- Martin
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
