From: "Ian Phillips" <ianp@tibco.com>
To: Seemant Kulleen <seemant@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Fonts, Xfree, Linux
Date: 30 May 2003 11:44:35 +0200 [thread overview]
Message-ID: <1054287874.1697.17.camel@pcianp> (raw)
In-Reply-To: <20030530023039.6f117918.seemant@gentoo.org>
> had a look at it (popt is a required dependency for it), and I've
> asked Graham (vladimir@g.o) to come up with a perl equivalent for it. To me, it seems that coding that in C and using popt is overkill.
Surely Python would be more Gentoo-ish?
As to files in /etc, how about this as a first hack: modify etc-update
so that an ebuild can mark a file in /etc as requiring manual attention
and possibly an optional short text message. I'm not sure of the best
way to do this, but maybe if etc-update finds an update file with some
magic string as the first line then it will say that the file needs
attention. The file could just be a pointer to the user to run
GentooFontUpdater or whatever the new tool is called.
It seems (more than) a little hacky, but I think that not touching files
in /etc is a good rule, and think it's worth putting some effort into a
way of not breaking it.
Ian.
--
#ifndef __COMMON_SENSE__ | Ian Phillips
#include <std_disclaimer> | TIBCO Software Inc.
#endif | www.tibco.com
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-05-30 9:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 9:30 [gentoo-dev] Fonts, Xfree, Linux Seemant Kulleen
2003-05-30 9:40 ` Paul de Vrieze
2003-05-30 9:44 ` Ian Phillips [this message]
2003-05-30 13:03 ` Terje Kvernes
2003-05-30 13:18 ` Seemant Kulleen
2003-05-30 13:31 ` Spider
2003-05-30 16:40 ` Svyatogor
2003-05-30 16:21 ` Svyatogor
2003-05-30 19:12 ` Dan Armak
2003-05-30 17:25 ` matsuu
2003-05-30 19:54 ` George Shapovalov
2003-05-31 18:04 ` Matthew Kennedy
2003-06-01 6:23 ` C. Brewer
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=1054287874.1697.17.camel@pcianp \
--to=ianp@tibco.com \
--cc=gentoo-dev@gentoo.org \
--cc=seemant@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