public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Armyr <daniel.armyr@home.se>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] (FS) Attributes for Ebuilds?
Date: Thu, 5 Jun 2003 10:00:36 +0200	[thread overview]
Message-ID: <20030605100036.05bb95d4.daniel.armyr@home.se> (raw)
In-Reply-To: <20030605152134.43bff13c.citizen428@cargal.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> b. you wouldn't have to build a new tool, filesystems
> capable of handling these kind of attributes have them already

Do Reiser/ext2/ext3 etc support this? If not, I assume this would mean one needs a separade partition for /usr/portage, no? Althought using allready available tools is a good thing, I feel needing yet another partition complicates things, as well allowing less HD space to be used.

My 2 CFLAGS
- --Daniel Armyr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+3vikhxtTUWLs2lERAikKAKCeTaB7n5UBCMnUQWtEsAvBJGgf9gCfQsUc
lWILmNIHkbl3VkkuNKMQdnc=
=3eJw
-----END PGP SIGNATURE-----

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-06-05  7:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05  6:47 [gentoo-dev] (FS) Attributes for Ebuilds? Michael Kohl
2003-06-05  7:02 ` Joseph Hardin
2003-06-05  7:21   ` Michael Kohl
2003-06-05  7:52     ` George Shapovalov
2003-06-05 10:17       ` Michael Kohl
2003-06-05  8:00     ` Daniel Armyr [this message]
2003-06-05  9:50       ` Marko Mikulicic
2003-06-05  9:17     ` Evan Powers
2003-06-05 12:23       ` Michael Kohl
2003-06-05  9:39 ` Georgi Georgiev
2003-06-05 14:43 ` Marius Mauch
2003-06-09 21:40 ` [gentoo-dev] " ross girshick
2003-06-10  2:46   ` Michael Kohl
2003-06-24 15:20     ` [gentoo-dev] "Updating Portage Cache" optimizations ross b girshick
2003-06-24 15:41       ` Seemant Kulleen
2003-06-24 15:56         ` ross b girshick
2003-06-24 16:08           ` Seemant Kulleen
2003-06-24 21:46             ` ross b girshick

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=20030605100036.05bb95d4.daniel.armyr@home.se \
    --to=daniel.armyr@home.se \
    --cc=gentoo-dev@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