9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: lucas.francesco93@gmail.com, 9front@9front.org
Subject: Re: [9front] move zlib source from ghostscript to ape/lib/z and update to latest zlib
Date: Sun, 15 Mar 2020 20:28:29 -0700	[thread overview]
Message-ID: <9848D509BA86811E2EE1458938877304@eigenstate.org> (raw)
In-Reply-To: <CAF=5iUXK-oaAXa-Y_GXjujckpNGPjTa4mfO4Dx-cy1vFHmsHdg@mail.gmail.com>

> Hey Cinap, I didn't mean harm with the patches, it was my bad to
> include contrib(I had a local zlib copy lingering for weeks with those
> contrib dirs, didn't notice I still had Pascal), I think with this one
> it can be made clear what changed and what didn't.

Thanks for updating!

This patch looks easier to review, but there seems to be some binary
junk at the end of it. Can you try resending?

> This patchset doesn't move out stuff from gs for now. Most of the diff
> is on the INDEX and the Changelog files alongside the new ones. (gzio
> became 4 different files, there's a new tests dir for the tests, some
> bugfixes and a new test.)

Out of curiosity, have you tried running the tests? Might be a good
sanity check.

> Take note: I've changed the mkfile cflags on this one, they seem to be
> fine, but its up to you guys to consider it uneeded or not, I guess
> this is not final.
> 
> as for using APE or not, I'd love to see some separation/at least get
> rid of gs for page eventually, but thats a distant future.
> 
> Em qui., 5 de mar. de 2020 às 16:18, <cinap_lenrek@felloff.net> escreveu:
>>
>> what i'd like to see is an actual diff of what changed in zlib. i cannot
>> belief there are too many changes. zlib is very old library. i'm very
>> curious why we need a specific version of zlib and what features did
>> they add.
>>
>> once we have a overview what we'r getting into, then we can move it out
>> of ghostscript.
>>
>> --
>> cinap



  reply	other threads:[~2020-03-16  3:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2020-03-02 23:08 kokamoto
2020-03-03  0:49 ` Steve Simon
2020-03-03  1:01   ` ori
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
2020-03-03  6:36 kokamoto
2020-03-03 11:05 kokamoto

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=9848D509BA86811E2EE1458938877304@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \
    --cc=lucas.francesco93@gmail.com \
    /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).