My proposal is to add a new local USE for fcron to switch the mailing capabilities on/off. The mailing stuff isn't needed by all people and therefore a flag would be great. Greetings
So don't use it, what's the point of this complaint?
Hmm, the configure script of fcron has the option to compile fcron with the flag --without-sendmail. As I *like* fcron (that's why I want to use it), but NOT want to have the mta-dependency, an appropriate USE flag would nice, wouldn't it? Perhaps you'll understand me better now, Greetings
I would like to see this either, since I do not need an mta at all. Unfortunately, the virtual/mta dependency is in the cron eclass, so this would need more than just a minor effort.
I don't feel comfortable changing the cron eclass. What's so problematic about getting mail-mta/ssmtp installed anyway? I mean, it's not a huge 10M package... I agree that it would be a preferable solution to be able to turn that MTA dependancy off, but as Sascha said, that would require more work than just adding a USE flag to the fcron ebuilds and changing its DEPEND. Too much work for too little gain, for my personal taste. So: sorry, but I won't do it.
(In reply to comment #4) > I don't feel comfortable changing the cron eclass. > What's so problematic about getting mail-mta/ssmtp installed anyway? Security and another unnecessary package to pay attention to. > its DEPEND. Too much work for too little gain, for my personal taste. > So: sorry, but I won't do it. Would it be acceptable if someone else did this? If so, I'll give it a shot. What USE flag (sendmail/mta/nosendmail/nomta...) would you like to see?
(In reply to comment #5) > (In reply to comment #4) > > I don't feel comfortable changing the cron eclass. > > What's so problematic about getting mail-mta/ssmtp installed anyway? > > Security and another unnecessary package to pay attention to. Security?! You know that ssmtp is not a daemon like sendmail/postfix/exim, but just a simple /usr/sbin/sendmail drop-in replacement? I don't see why this package would cause any impact on system security or why you would have to pay attention for it after the installation. > > its DEPEND. Too much work for too little gain, for my personal taste. > > So: sorry, but I won't do it. > > Would it be acceptable if someone else did this? I won't commit anything I'm not going to take responsibility for.
