public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Martin MOKREJŠ" <mmokrejs@ribosome.natur.cuni.cz>
To: gentoo-dev@robin.gentoo.org
Subject: [gentoo-dev] New net-fs/openafs ebuild
Date: Wed, 13 Apr 2005 12:44:40 +0200	[thread overview]
Message-ID: <425CF818.5080700@ribosome.natur.cuni.cz> (raw)

Hi,
  I've prepared an updated net-fs/openafs ebuild. The original reason was that
virtually all documentation is based on the style IBM/Transarc have installed it, i.e.
into /usr/afs, /usr/vice and /usr/afsws prefixes.

  openafs-1.2 supports only 2.4 kernels. 2.6 kernels are supported only in 1.3. series,
at the moment 1.3.81 is reaching 1.4 release and support largefiles and 2.6 kernel.

  Based on response from Ryan Phillips, I'd like to ask you to give some feedback to
the proposed ebuild. The ebuild works but have some questions (as comments in the
file itself), mostly related to the way files from sourcetree are copied/installed
into target.

  I'm not sure how to block the ebuild when user is running 2.6 kernel (uname(1)?),
of when the /usr/src/linux points to 2.6 kernel ... or just to check whether
gentoo-sources or vanila-sources of 2.4 version are installed?

  The original bugreport and the ubuilds are at
http://bugs.gentoo.org/show_bug.cgi?id=69649

Thanks for help!
-- 
Martin Mokrejs
Email: 'bW9rcmVqc21Acmlib3NvbWUubmF0dXIuY3VuaS5jeg==\n'.decode('base64')
GPG key is at http://www.natur.cuni.cz/~mmokrejs
--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2005-04-13 10:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 10:44 Martin MOKREJŠ [this message]
2005-04-13 13:06 ` [gentoo-dev] New net-fs/openafs ebuild Mike Frysinger
2005-04-13 13:13   ` Jason Stubbs
2005-04-13 14:17     ` Georgi Georgiev
2005-04-13 14:36       ` Jason Stubbs
2005-04-13 14:28     ` Martin MOKREJŠ
2005-04-13 14:38       ` Mike Frysinger

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=425CF818.5080700@ribosome.natur.cuni.cz \
    --to=mmokrejs@ribosome.natur.cuni.cz \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-dev@robin.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