From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DMARC_NONE,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from smtp.giga.ocn.ne.jp (giga.ocn.ne.jp [211.129.14.85]) by chiba.3jane.net (Postfix) with ESMTP id 022B0ABD4F; Thu, 30 May 2002 22:32:09 -0500 (CDT) Received: from [192.168.1.11] (p14090-adsao09hon-acca.tokyo.ocn.ne.jp [61.127.128.90]) by smtp.giga.ocn.ne.jp (Postfix) with ESMTP id 9307B53E7; Fri, 31 May 2002 12:32:06 +0900 (JST) From: Ryan Shaw To: gentoo-dev@gentoo.org Cc: pvdabeel@gentoo.org, mark@cs.columbia.edu Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 31 May 2002 12:26:18 +0900 Message-Id: <1022815579.5279.5.camel@momo> Mime-Version: 1.0 Subject: [gentoo-dev] Emacs ebuild and LEIM Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 24d752d4-9b7d-4bd2-945f-c2ab4150c517 X-Archives-Hash: 2f2d63b93bce2233ce6e6c69dd6e8d99 Hello, 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 tarball 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? Or is this something that could be added to the emacs ebuild, possibly governed by a new USE variable (say "multi-byte" for apps that have compile-time options for multi-byte charset support)? Please let me know your thoughts. Ryan