On Mon, Mar 10, 2008 at 02:54:48PM -0400, Stephen Talley wrote:
> The configuration in /etc isn't random -- it is a small set of sane
> defaults that the mutt developers have determined to be generally
> useful. I personally do rely on this configuration. Forcing users to
> duplicate this default configuration in their own .muttrc seems unduly
> burdensome. It would also be inconsistent with other OSs that ship
> mutt.
Okay. I'll note that gentoo ships an empty Muttrc (save for a few lines of
comments exhorting admins to put nothing there), while ubuntu ships a
fairly complicated one that loads a directory full of sub-rc files and does
a bunch of wacky things.
The default one that ships with Mutt does seem pretty sane. However, you
might want to change the line that references the manual from /usr/local to
point to the appropriate path.
> [fetchmailconf.py] is not imported by anything else in the package. I do
> not know whether the intent of the developer was to make it available for
> import elsewhere, so leaving it in vendor-packages and linking to it
> seems like the safest choice. If you feel strongly about this, I
> can install it directly in usr/bin.
Erm. I'd certainly feel strongly enough if it were our own code, but less
so since it's someone else's. You might ping the authors or whatever
fetchmail development list that might exist and see what people think, but
there's no point in waiting a long time for a response.
> > SUNWfetchmail/Makefile:
> >
> > o line 30: If you're going to start pulling prototype_{i386,sparc}
> > from common_files, then you should probably do this for the rest
> > of the packages, too. If that doesn't appeal, do it the way
> > everyone else does.
>
> Done.
Wow. Seriously.
Danek
