From: "Alexey Shabalin" <a.shabalin@gmail.com>
To: "ALT Linux Team development discussions" <devel@lists.altlinux.org>
Subject: Re: [devel] Q(GNOME): gconf schemes location
Date: Tue, 6 May 2008 14:29:02 +0400
Message-ID: <b966c1e40805060329u5b8ab99dp37ba0eaaa34266bd@mail.gmail.com> (raw)
In-Reply-To: <1210068646.12991.8@ildar.innovations.kz>
6 мая 2008 г. 14:10 пользователь Ildar Mulyukov написал:
> On 06.05.2008 15:25:44, Igor Vlasenko wrote:
>
> > Возник вопрос по gconf-devel макросам и упаковке gconf-schemas.
> >
> > В debian принято следующее полиси -
> >
> > Tag: package-installs-into-etc-gconf-schemas
> > Type: warning
> > Info: The package installs files into the <tt>/etc/gconf/schemas</tt>
> > directory. No package should do this; this directory is reserved for
> > local overrides. Instead, schemas should be installed into
> > <tt>/usr/share/gconf/schemas</tt>.
> >
> > мы же собираем все в /etc/gconf/schemas.
> >
> > Не разумнее ли в данном вопросе стырить полиси из debian?
> IMHO да
А смысл? Мы кладём в /etc/gconf/schemas уже пропатченные схемы, в rpm
они помечены как config.
Предлагается класть дефолтные(от gnome) схемы в
/usr/share/gconf/schemas, а в /etc наши изменённые? Зачем увеличение
сущьностей? Сделать конечно можно, только кому это облегчит жизнь?
Какова цель?
--
Alexey Shabalin
next prev parent reply other threads:[~2008-05-06 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 9:25 Igor Vlasenko
2008-05-06 10:10 ` Ildar Mulyukov
2008-05-06 10:29 ` Alexey Shabalin [this message]
2008-05-06 10:34 ` Igor Vlasenko
2008-05-08 12:09 ` Alexey I. Froloff
2008-05-08 15:15 ` Igor Vlasenko
2008-05-08 17:41 ` Alexey I. Froloff
2008-05-12 11:39 ` [devel] warning for /etc/hal/fdi/policy/* Igor Vlasenko
2008-05-06 10:36 ` [devel] Q(GNOME): gconf schemes location Ildar Mulyukov
2008-05-21 13:19 ` Alexey Rusakov
2008-05-14 0:00 ` Alexey Rusakov
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=b966c1e40805060329u5b8ab99dp37ba0eaaa34266bd@mail.gmail.com \
--to=a.shabalin@gmail.com \
--cc=devel@lists.altlinux.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
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git