From: "Jared H. Hudson" <jhhudso@volumehost.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] /usr/spool/mail versus maildir: use item needed
Date: Thu, 18 Apr 2002 22:44:12 -0500 [thread overview]
Message-ID: <3CBF928C.2000007@volumehost.com> (raw)
In-Reply-To: 20020418221743.5825EAC4FE@chiba.3jane.net
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.
>>
>
>
prev parent reply other threads:[~2002-04-19 3:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 22:55 [gentoo-dev] /usr/spool/mail versus maildir: use item needed Jared H. Hudson
2002-04-17 23:08 ` Grant Goodyear
2002-04-18 12:55 ` Arcady Genkin
2002-04-18 19:37 ` Jared H. Hudson
2002-04-18 19:49 ` Grant Goodyear
2002-04-18 20:34 ` Thilo Bangert
2002-04-18 21:58 ` Jared H. Hudson
2002-04-18 22:12 ` Thilo Bangert
2002-04-19 3:44 ` Jared H. Hudson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CBF928C.2000007@volumehost.com \
--to=jhhudso@volumehost.com \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox