From: ori@eigenstate.org
To: steve@quintile.net, 9front@9front.org
Subject: Re: [9front] move zlib source from ghostscript to ape/lib/z and update to latest zlib
Date: Mon, 2 Mar 2020 17:01:17 -0800 [thread overview]
Message-ID: <B89D4ECE0800262103215122680CC112@eigenstate.org> (raw)
In-Reply-To: <2D34807C-E2F4-4C1D-B84F-583D2AAC9A88@quintile.net>
> there was a program in comp.sources.unix (or maybe misc) called unifdef which would apply selective conditionals and oreserved comments. it is so old it is orobably pre andi and may not know about c++ style comments, but maybe it would help.
>
> itwould allow you tokeep only the os support you need - and make the code mire readable perhaps.
>
On one hand, yes -- unifdef will let you do that. On the other hand,
unless we make a considered choice to fork fully and actually
*maintain* a forked version of the initial code, I think it's better
to keep the sources of ported code as close to upstream as possible,
so that it's easy to import new versions and update it -- and submit
portabillity fixes to the maintainers, so we don't have to move them
along manually to new versions.
In general, plan 9 ports have the problem of being off-brand tarballs
that, to a good approximation, never get updated.
I think it's worth trying to change that situation, so we actually
maintain the things we decide are worth porting.
next prev parent reply other threads:[~2020-03-03 1:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 23:08 kokamoto
2020-03-03 0:49 ` Steve Simon
2020-03-03 1:01 ` ori [this message]
2020-03-03 10:06 ` hiro
2020-03-03 10:08 ` hiro
2020-03-03 10:12 ` hiro
2020-03-03 14:01 ` ori
2020-03-03 13:58 ` ori
-- strict thread matches above, loose matches on Subject: below --
2020-03-03 11:05 kokamoto
2020-03-03 6:36 kokamoto
2020-03-02 5:15 Lucas Francesco
2020-03-02 8:33 ` [9front] " cinap_lenrek
2020-03-02 14:41 ` ori
2020-03-05 19:17 ` cinap_lenrek
2020-03-08 23:44 ` Lucas Francesco
2020-03-16 3:28 ` ori
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=B89D4ECE0800262103215122680CC112@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=steve@quintile.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).