zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <zefram@fysh.org>
To: kura@pld.org.pl
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: Gettext, cproto, configure, license
Date: Sat, 29 Jan 2000 07:50:31 +0000 (GMT)	[thread overview]
Message-ID: <E12ESeN-0005ra-00@crucigera.fysh.org> (raw)
In-Reply-To: <20000129000341.A1459@pld.org.pl> from Michal Kuratczyk at "Jan 29, 2000 00:03:41 am"

Michal Kuratczyk wrote:
>- using gettext to provide localized messages

We discussed locale usage recently.  I think this is the only type
of locale usage that would be uncontroversial.  It's just a matter of
someone producing the (inevitably large) code patch, and someone doing
translations.

>- using 'cproto' instead of awk script and strange formatting

The awk script does a lot besides just generating prototypes.  And we
can't rely on cproto being available on every build system (I don't have
it here, for example, and this is a recent Red Hat).

>- adding configure option to provide building minimal version of zsh
>  (for using as a /bin/sh or as a rescue tool). Only POSIX-sh
>  capabilities whould be available in such version.

That's something I'm planning.  There's some work to do with modules
first.

>I created RPM package with zsh, but I am not sure how should I call the
>license. Usuall in RPM packages one uses keywords like 'public domain',
>'distributable', 'GPL' or something like that. What should I put there?

It's the zsh license -- it's unique to zsh.  Its effect is pretty much
identical to the BSD license, so you could reasonably describe it as
"BSD-like".

I'd much rather we used one of the standard licenses (and actually I've
changed my mind recently and come to quite like the GPL).  But we've
already changed the license twice that I remember, and it's a complex
issue, so I don't see us switching any time soon.

-zefram


      reply	other threads:[~2000-01-29  7:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-28 23:03 Michal Kuratczyk
2000-01-29  7:50 ` Zefram [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=E12ESeN-0005ra-00@crucigera.fysh.org \
    --to=zefram@fysh.org \
    --cc=kura@pld.org.pl \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).