From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: tech@mdocml.bsd.lv
Subject: Re: implement .so
Date: Sun, 24 Oct 2010 18:49:45 +0200 [thread overview]
Message-ID: <20101024164945.GA25275@britannica.bec.de> (raw)
In-Reply-To: <20101024164057.GF20876@iris.usta.de>
On Sun, Oct 24, 2010 at 06:40:57PM +0200, Ingo Schwarze wrote:
> not only Xenocara (i.e. OpenBSD X.org), but various ports as well
> use .so. I'm not thrilled about that, i think .so is useful for
> general-purpose typesetting, but rather dumb in a manual formatter.
> Yet, being even less thrilled about the prospect to rewrite the
> X.org build system or about patching lots of ports, i made up my
> mind to implement .so.
I don't think any patching itself has to be done. There is already a
tool called soelim to expand them statically. Remember that we discussed
.so in Rostock? The behavior is not exactly sane. So from a maintainance
perspective, I think it is much easier to just handle the 99% of easy
cases in ports/pkgsrc and patch the few remaining cases.
Joerg
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-10-24 16:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 16:40 Ingo Schwarze
2010-10-24 16:49 ` Joerg Sonnenberger [this message]
2010-10-24 17:29 ` Ingo Schwarze
2010-10-24 17:38 ` Joerg Sonnenberger
2010-10-24 18:00 ` Ingo Schwarze
2010-10-24 18:15 ` Joerg Sonnenberger
2010-10-24 18:17 ` Joerg Sonnenberger
2010-10-24 19:41 ` Ingo Schwarze
2010-10-24 19:51 ` Joerg Sonnenberger
2010-10-25 21:55 ` Ingo Schwarze
2010-10-25 22:10 ` Joerg Sonnenberger
2010-10-26 17:59 ` Ingo Schwarze
2010-10-26 18:12 ` Joerg Sonnenberger
2010-10-26 21:48 ` Ingo Schwarze
2010-10-26 21:56 ` Joerg Sonnenberger
2010-10-26 23:10 ` Ingo Schwarze
2010-10-26 23:30 ` Joerg Sonnenberger
2010-10-26 23:41 ` Ingo Schwarze
2010-10-27 9:34 ` Kristaps Dzonsons
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=20101024164945.GA25275@britannica.bec.de \
--to=joerg@britannica.bec.de \
--cc=tech@mdocml.bsd.lv \
/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).