Re: [gentoo-dev] /usr/spool/mail versus maildir: use item needed

[Jared H. Hudson]

For example in procmail right now, the procmail ebuilder uses sed to 
edit the procmail source to use maildir at ~/.maildir instead of 
/usr/spool/mail

I was going to add a use line so people can use the original mbox style 
/var/spool/mail, or if they choose maildir let MAILDIR_PATH tell the sed 
script what to change it to, that way it can be ~/Maildir or ~/.maildir

The same idea could apply to ebuild foo config when a user chooses to 
let ebuild configure their email server, ect. Note this config is 
optional and for most people would just be a start to configuring such 
an app. For example ebuild php-* config adds php stuff to apache, but of 
course anyone who runs apache is going to edit their config file as well 
most likely.

-Jared H.

Thilo Bangert wrote:
> On Thursday, 18. April 2002 23:58, you wrote:
>
>>>>use items:
>>>>mbox and maildir
>>>
>>>what about the idea of just having one? (as they rarely will be
>>>used at the same time anyway)
>>>
>>>hhm, i guess you can compile pine with support for both.. (?)
>>
>>What do you mean just having one? It makes sense to me for a user to
>>put mbox or maildir in their USE items. Several programs, like pine,
>>procmail, ect can handle both formats. And with patches more programs
>>can handle both. So I think we need both use lines and have a user
>>choose one, otherwise the default for that package will be chosen.
>>
>
>
> yes, you are right.
>
>
>>I thought about the MAIL variable, and it would make sense, unless
>>you were wanting to compile for another machine, hence a specifically
>>defined MBOX_PATH or MAILDIR_PATH makes more sense, IMO.
>
>
> i don't know the package that uses this, as i can not think of why this
> would be a compile time variable...
>
> IMHO this should only be a runtime variable, because of the fact, that
> (at least in some cases) it is up to the user to decide
>
> so what package needs this?
>
>
>>-Jared H.
>>
>
>