public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Upcoming LyX ebuild - design questions
Date: Wed Jul 11 12:58:01 2001	[thread overview]
Message-ID: <20010711125703.K22717@cvs.gentoo.org> (raw)
In-Reply-To: <01071114294901.00551@localhost>; from ermak@netvision.net.il on Wed, Jul 11, 2001 at 02:29:49PM +0300

On Wed, Jul 11, 2001 at 02:29:49PM +0300, Dan Armak wrote:

> 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.

Well, have it depend on 1, 2 and 3.  We want the base install of our packages
to be fully-functional, and tetex and ghostscript and a postscript viewer would
be needed to actually use Lyx for anything useful.

I'm hoping that the things in 4 and 5 can be built as separate packages rather
than being included in the main Lyx package.  If this is possible, that's what
I would recommend as well.

> 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?

A good solution, since it gives our users more flexibility.

> ----
> 
> Another issue: whould Lyx go into app-text (as a latex frontend) or into 
> app-office (as a word processor)?
> 
> ----

I'd put it in app-text.

> 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. :-)

Well, that's why we're glad that you're around :))

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			



      parent reply	other threads:[~2001-07-11 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-11  5:33 [gentoo-dev] Upcoming LyX ebuild - design questions Dan Armak
2001-07-11  8:25 ` Terje Kvernes
2001-07-11 12:58 ` Daniel Robbins [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=20010711125703.K22717@cvs.gentoo.org \
    --to=drobbins@gentoo.org \
    --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