Re: --lock-flags now configurable, and some mu_argp reorg

[Sam Roberts]

Quoteing address@hidden, on Thu, Apr 11, 2002 at 09:43:36AM -0400:
> > 
> > > - mailutils allows you to write non-GPL programs, those programs
> > 
> > Excuse me, but I believe it does not. The COPYING file states that
> > the whole suite is distributed under GPL, which means that any
> > derivative work must be distributed under the same conditions as those
> > set forth in the GPL.
> 
> Sam, mailutils/mailbox/*.[ch] is cover by LGPL but all the other programs
> and supported mailutils/lib/* are GPL.  So programs are distributed
> in terms of GPL and mu_argp_parse(), I beleive is only use in applications
> not the core lib API.

My understanding is:

mailutils/COPYING is the LGPL

mailutils/mailbox is LGPL

The distributed utilities are GPLed.

lib/*.c EXCEPT mu_argp.c is LGPL, sorry, I assumed all of lib/* was
under the same licence.

So it looks like it isn't possible to use mu_argp_parse under LGPL.

sieve, btw, is based on a CMU library, which is a BSD-style licence.

So, I don't think I can use it in a non-GPL application (sieve/sieve.c
is LGPLed). Am I correct?

Correct?

> > > - just because there are other mail and from and sieve utilities in
> > >   the world, doesn't mean that I should have to rename the config
> > >   files for mine as ~/.mu.???rc, IMHO. It is handy to isolate/group
> > >   rcfiles sometimes, though, so now if ~/.mailutils is a directory,
> > >   then that directory is searched for the rc files, instead of ~/.
> > > 
> > >   I can add back the .mu. prefix for config files if thats not
> > >   sufficient, but I really like the directory of config files, an
> > >   idea I shamelessly stole from mutt.

Ok, I added the .mu. back in.

No objections to the ~/.mailutils as a directory, then?

Cheers,
Sam

-- 
Sam Roberts <address@hidden> (Vivez sans temps mort!)