zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <schizo@debian.org>
To: Oliver Kiddle <opk@u.genie.co.uk>
Cc: zsh-workers@sunsite.dk
Subject: Re: PATCH: honor STRIPFLAGS for modules
Date: Thu, 19 Apr 2001 15:47:47 -0400	[thread overview]
Message-ID: <20010419154747.A9412@dman.com> (raw)
In-Reply-To: <3ADF3C5B.A508F9E2@u.genie.co.uk>; from opk@u.genie.co.uk on Thu, Apr 19, 2001 at 08:28:27PM +0100

> I'm not sure that I understand the difference. I only just realised that
> on Linux termcap and curses are symlinked - yuk. So I guess the initial

That's not always true.  Some systems have a libtermcap which is merely
libtermcap, not some sort of (n)curses termcap emulation.

> patch was removing the duplicates by doing symbol searches to detect if
> termcap/curses are one and the same which is fair enough provided there
> is some tangible benefit of not linking both. If you say it makes a

No, the original point of this was to link the termcap module with
whatever has tgetent() and the terminfo module with whatever has tigetstr().
On Debian, for instance, they're both covered by ncurses, but elsewhere
there can be conflicts.

> difference on Linux then fine. I'm just not clear on why it was an
> improvement other than possibly making the compile system cleaner. If
> I'm asking stupid questions, ignore me: normally I'd have assumed you
> know what you're doing and kept quiet if I didn't fully understand but
> in this case I'm afraid I didn't.

No, I clearly don't know what I'm doing or I would have gotten it right
the first time.

> So, this latest patch seems to be separating LIBS, and MAINLIBS for DSOs
> and the main zsh binary - right? It sounds to me from the discussion
> though that we almost need a separate $LIBS for every single module
> though which is a bit worrying. Is the initial thing which has sparked
> this off that the termcap/terminfo modules are the first modules which
> are using libraries which the main zsh never previously loaded? Could
> LIBS maybe remain just the common libraries and we then add the extra
> libraries for the termcap module only?

Originally, you would only get the terminfo module if whatever
library selected for termcap also did terminfo.  This was, IIRC,
because people didn't want terminfo libraries linked against
the main binary just for the sake of a module that they would
not use.  Obviously that's gotten more complicated now.

> Also, a while back when you implemented ${(k)terminfo} you asked if you
> should also do this for termcap. Sorry if this is already done but if
> not, I'd just like to add my vote in favour, even if you need to
> constant table of termcap codes - it'd be useful.

I had started this and then lost my changes due to a system crash,
but I'll restart it soon.


      reply	other threads:[~2001-04-19 19:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-19  1:39 Clint Adams
2001-04-19  2:24 ` Zefram
2001-04-19 11:18 ` Oliver Kiddle
2001-04-19 12:40   ` Clint Adams
2001-04-19 17:15     ` Oliver Kiddle
2001-04-19 17:46       ` Clint Adams
2001-04-19 19:28         ` Oliver Kiddle
2001-04-19 19:47           ` Clint Adams [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=20010419154747.A9412@dman.com \
    --to=schizo@debian.org \
    --cc=opk@u.genie.co.uk \
    --cc=zsh-workers@sunsite.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).