From: Manish Singh <manish.singh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2-1.0.1 ebuilds
Date: Mon Aug 15 17:14:45 2005 [thread overview]
Message-ID: <20050815221450.GA29912@ca-server1.us.oracle.com> (raw)
In-Reply-To: <43010710.2060800@yu.net>
On Mon, Aug 15, 2005 at 11:20:16PM +0200, lazar obradovic wrote:
> Gentoo ocfs2 1.0.1 ebuilds are available from
> http://bugs.gentoo.org/show_bug.cgi?id=98024
A few comments and questions:
> KEYWORDS="-* ~x86"
Does that mean this is only enabled for x86 platforms? 1.0.x works on
x86_64 and ia64 too.
The glib2 dependency in the tools should not be in the gtk2 option,
since ocfs2cdsl and debug.ocfs2 depend on it too, and they are command
line tools. Passing --disable-gtktest in the non-gtk2 case is kind of
silly, since there isn't any test for gtk itself, only pygtk.
The python binding for VTE is needed for some ocfs2console functionality
(though it does work without it).
Why are you using --prefix=/ ?
It looks like you are still installing a sample cluster.conf. This makes
no sense, there's no sane defaults for it, and putting the sample will
only lead to confusion.
Replacing the o2cb init script with your own is a bad idea. This makes
the gentoo distribution gratuitiously incompatible with the OCFS2
documentation out there, as well as breaking some ocfs2console
functionality. Please don't do this.
-Manish
next prev parent reply other threads:[~2005-08-15 17:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 20:03 [Ocfs2-devel] ocfs2-1.0.0 ebuilds lazar obradovic
2005-08-15 16:19 ` [Ocfs2-devel] ocfs2-1.0.1 ebuilds lazar obradovic
2005-08-15 17:14 ` Manish Singh [this message]
2005-08-15 17:29 ` Sunil Mushran
2005-08-15 18:46 ` lazar obradovic
2005-08-15 19:35 ` Manish Singh
2005-08-15 18:23 ` lazar obradovic
2005-08-15 19:26 ` Manish Singh
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=20050815221450.GA29912@ca-server1.us.oracle.com \
--to=manish.singh@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.