From: Dan Armak <ermak@netvision.net.il>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] Upcoming LyX ebuild - design questions
Date: Wed Jul 11 05:33:02 2001 [thread overview]
Message-ID: <01071114294901.00551@localhost> (raw)
Hi all,
I'm about to post my LyX ebuild, which depends on the gv and Xaw3d ebuilds I
posted earlier.
There are however some design questions I'd like to clear up first:
LyX is a word processor based on LaTeX, a very good one IMHO. LyX can make
use of a great number of packages, but it can also do withuot them. Which of
the following package groups should the LyX ebuild depend on?
1. Absolutely necessary packages: x11 & gtk.
2. latex2e and a few other things, all of which are in tetex. Lyx can build
and run without these, but it'd be just a flashy text editor without any
output capabilities.
3. Important utilities like ghostscipt and gv, to use for viewing your output.
4. A _very_ large amount of third-party exporters, importers, converters and
viewers. Enables you to output in many formats etc.
5. A few misc tex packages like the one for Hebrew support (which I use) that
aren't included in tetex.
Which of these should the ebuild force (i.e. DEPEND on)?
An idea: building a lyx-base ebuild which only depends on x11/gtk and a lyx
ebuild which does nothing but depends on lyx-bsae, tetex and everything else.
Maybe with another in-between stage (i.e. a lyx-utils ebuild).
What do you think?
----
Another issue: whould Lyx go into app-text (as a latex frontend) or into
app-office (as a word processor)?
----
And finally: does anybody here except myself use LyX? Because I can't
understand how such a great distro cold live so long without this
all-important package. :-)
Dan
next reply other threads:[~2001-07-11 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 5:33 Dan Armak [this message]
2001-07-11 8:25 ` [gentoo-dev] Upcoming LyX ebuild - design questions Terje Kvernes
2001-07-11 12:58 ` Daniel Robbins
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=01071114294901.00551@localhost \
--to=ermak@netvision.net.il \
--cc=gentoo-dev@cvs.gentoo.org \
/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