bug-mailutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] put some support optional at configure time


From: Sergey Poznyakoff
Subject: Re: [PATCH] put some support optional at configure time
Date: Thu, 24 Oct 2002 03:21:34 +0300

> > So, the patch is attached (in unidiffs format ;-) ).
> 
> hmm ... This an area where sergey been working on, I'll let him
> handle it .. but I think he's on vacation "living la vida loca"

Yeah, that's exactly the right word :^) As I see I have missed quite
a number of interesting postings from Olivier. I'll try to answer them
all in one letter:

1) Re: [PATCH] removing imap (and other) support

Thanks for the patch. The simple calculation shows:

$ cd mailbox
$ size folder_imap.o folder_mbox.o folder_mh.o folder_pop.o mbx_imap.o
mbx_mbox.o mbx_mh.o mbx_pop.o|awk 'NR==1 {} { sum += $4 } END { print
$4 }'
115224

i.e. the patch allows to save about 112K space at maximum.

I will need some time to apply the changes. By the way what is the
project for which 112K constitute a major saving?

2) Re: Must macros in m4 be GPL or LGPL

> it's maybe better to have the macros in the directory
> m4 be LGPL licensed, as they are used for making the mailutils
> libraries. 

GPL describes the copying conditions for the program under it
and any derivative works, based on this program (derivative is "a work
containing the Program or a portion of it"). It does not impose any
restrictions on the use of any data produced by using the program, since
such data does not in itself constitute a derivative work. The GPL
states (paragraph 0):

  "The act of running the Program is not restricted, and the output"
  "from the Program is covered only if its contents constitute a work"
  "based on the Program (independent of having been made by running
  "the Program). Whether that is true depends on what the Program"
  does."

As an example, gcc can be (and often is) used to build proprietory software.
The scripts in m4/ are used to build the configuration-dependent data,
which do not constitute a work based on the scripts. Thus, GPL is
quite OK.

3) Re: pop3d name inconsistency

[The question was whether a tool should use the name of its binary or
some standard name when outputting help info, diagnostics, etc.]

> I have answer for the process name and the binary name. For the entry in
> the log, I don't know. Maybe one of the current developper can answer to
> this point.

I believe the log message should contain the actual program name, i.e.
the binary name. I'll fix it.

4) Re: doc not up-to-date
5) Re: [PATCH] documentation update  

Thanks for the patches. I'll apply them this weekend.

Regards,
Sergey






reply via email to

[Prev in Thread] Current Thread [Next in Thread]