From: Ryan Shaw <ryan.shaw@stanfordalumni.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Ebuild for Emacs LEIM
Date: Wed, 15 May 2002 16:21:54 +0900 [thread overview]
Message-ID: <20020515162154.19c3dc37.ryan.shaw@stanfordalumni.org> (raw)
Hi,
I am planning on doing an ebuild for the Libraries of
Emacs Input Methods, or LEIM. The way these are usually
built from source is:
1) the emacs src tarball is downloaded and extracted,
2) the matching (same version) leim tarbell is downloaded
and extracted into the same dir (creating a new src subdir),
3) emacs is built and installed as normal.
It would be nice if the leim ebuild could be written in
such a way as to depend on the emacs ebuild, in which
case all the leim ebuild would need to specify is where
to get the leim src tarball. Everything else is already
done in the emacs ebuild.
My question: is there a way to do this? Or does there
need to be a new emacs-leim ebuild that conflicts with,
and mostly replicates, the emacs ebuild?
Cheers,
Ryan
next reply other threads:[~2002-05-15 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 7:21 Ryan Shaw [this message]
2002-05-15 7:50 ` [gentoo-dev] Ebuild for Emacs LEIM James Vandenberg
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=20020515162154.19c3dc37.ryan.shaw@stanfordalumni.org \
--to=ryan.shaw@stanfordalumni.org \
--cc=gentoo-dev@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