From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Problem writing my first ebuild
Date: Sat, 15 Jun 2002 01:09:24 +0200 [thread overview]
Message-ID: <20020615010924.45b657a7.degrenier@easyconnect.fr> (raw)
Hi,
I'm trying to write an ebuild for "xawdecode", a TV program based on "xawtv". I've based on xawtv-3.7.2.ebuild, but I have a problem: a few files, some fonts to go in /usr/X11R6/lib/X11/fonts/misc, are shared by this two program, so I can't emerge my application because of a sandbox write lock. How are we supposed to deal with this kind of incompatibility ? I've though about patching the Makefile to place the font somewhere else, but I don't feel it really satisfying.
Thanks for your advice,
-- Thomas.
next reply other threads:[~2002-06-14 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 23:09 Thomas de Grenier de Latour [this message]
2002-06-14 23:35 ` [gentoo-dev] Problem writing my first ebuild Chad M. Huneycutt
2002-06-15 0:08 ` [gentoo-dev] " Thomas de Grenier de Latour
2002-06-14 23:52 ` Thomas de Grenier de Latour
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=20020615010924.45b657a7.degrenier@easyconnect.fr \
--to=degrenier@easyconnect.fr \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@lists.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