zsh-workers
 help / color / mirror / code / Atom feed
* Gettext, cproto, configure, license
@ 2000-01-28 23:03 Michal Kuratczyk
  2000-01-29  7:50 ` Zefram
  0 siblings, 1 reply; 2+ messages in thread
From: Michal Kuratczyk @ 2000-01-28 23:03 UTC (permalink / raw)
  To: zsh-workers

Hi,

What do you think about:
- using gettext to provide localized messages
- using 'cproto' instead of awk script and strange formatting
- 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.

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?

PS Sorry, that I sent my previous mail to zsh-workers instead of zsh-users.
-- 
Michal 'kura' Kuratczyk <kura@pld.org.pl>
GC{S,M} d- s+:+ a18 C+++ UL++ L+++ E--- W
P- N++ w-- O- t--- X+ b- DI+ e- h* r++ y?


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Gettext, cproto, configure, license
  2000-01-28 23:03 Gettext, cproto, configure, license Michal Kuratczyk
@ 2000-01-29  7:50 ` Zefram
  0 siblings, 0 replies; 2+ messages in thread
From: Zefram @ 2000-01-29  7:50 UTC (permalink / raw)
  To: kura; +Cc: zsh-workers

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2000-01-29  7:50 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-01-28 23:03 Gettext, cproto, configure, license Michal Kuratczyk
2000-01-29  7:50 ` Zefram

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).