From: Bengt Kleberg bengt@softwell.se
Subject: [9fans] Re: licence terms
Date: Thu, 18 May 2000 11:45:52 +0200 [thread overview]
Message-ID: <20000518094552.h5r_Cg1VqxcyZ6HUlh2y0ZUyMvBkSc4iV7hFE3LpyH4@z> (raw)
Greetings,
I use OpenBSD at work. This way I know that when I ship software to a customer
(who probably uses Solaris or HP/UX or AIX ...) I can include any library functions
I have used, if they do not exist in the target environment.
What are the chances of doing the same with software developed on Plan9?
I am aware that most interesting programs uses per-process name spaces
and would be totally unportable, but what about all those un-interesting
programs that I get payed to write?
And yes, this does assume that plan9 library functions can be made to work on unix,
something that libXg and newsqueak has proved to a certain extent.
Best Wishes, Bengt
===============================================================
Everything aforementioned should be regarded as totally private
opinions, and nothing else. bengt@softwell.se
``His great strength is that he is uncompromising. It would make
him physically ill to think of programming in C++.''
reply other threads:[~2000-05-18 9:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20000518094552.h5r_Cg1VqxcyZ6HUlh2y0ZUyMvBkSc4iV7hFE3LpyH4@z \
--to=9fans@9fans.net \
/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.
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).