I've some new ebuilds: net-dialup/fcdsl is a CAPI-driver (ISDN and DSL) for the AVM Fritz!Card DSL. net-mail/messagewall is a smtp-proxy with some nice features. This ebuild needs two libs (firestring and firedns) for which I also wrote the ebuilds. The ebuilds could be found at: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/gentoo-deutsch/ebuilds/net- dialup/fcdsl/ http://cvs.berlios.de/cgi-bin/viewcvs.cgi/gentoo-deutsch/ebuilds/net- mail/messagewall/ http://cvs.berlios.de/cgi-bin/viewcvs.cgi/gentoo-deutsch/ebuilds/dev- libs/firedns/ http://cvs.berlios.de/cgi-bin/viewcvs.cgi/gentoo-deutsch/ebuilds/dev- libs/firestring/ Regards, Alexander Reproducible: Always Steps to Reproduce: 1. 2. 3.
I have a few concerns about this bug. First, I think they should be split into their bug-per-package so they can be appropriately assigned. For example, before I stomp on anyone's toes in dev-libs or net-mail, those devs should atleast get a peek, no? I realize that it is all part of one package, but those three ebuilds should get tagged for one bug and the fcdsl for another. Also the descriptions leave a tiny bit to be desired, e.g. what does fcdsl provide that isn't in say the capi4k-utils? or another package? Also, the ebuilds would do better if they were actually attached to the bugs they were for, just incase something happens to the page you're linking to. Last thing is, there's no sign of anything like "I'm currently running these packages from these ebuilds I've created, and they work for me" or anything like that. Can you confirm they atleast work for you on the third tuesday of the eight month during a solar eclipse? (or atleast say you built them from the ebuild you're supplying, people are often hestitant to run something no one else has tried). I'd appreciate an appropriate resubmittal, thanks:)
I don't write documentation. A driver is a driver. What else to say? That answer is just what I assumed. ;) Regards, Alexander
