public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Evan Powers <powers.161@osu.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] (FS) Attributes for Ebuilds?
Date: Thu, 5 Jun 2003 05:17:38 -0400	[thread overview]
Message-ID: <200306050517.38134.powers.161@osu.edu> (raw)
In-Reply-To: <20030605152134.43bff13c.citizen428@cargal.org>

On Thursday 05 June 2003 03:21 am, Michael Kohl wrote:
> Joseph Hardin <jhlazer@charter.net> wrote:
> > Why do this at a filesystem level? I may be missing the point, but why
> > not just incorporate this into a seperate tool and keep a file to
> > store all the comments and data.
>
> Because:
...

If you haven't already, you should read Hans Reiser's Future Visions document, 
here:

http://www.namesys.com/whitepaper.html

The summary is, in brief, that ReiserFS 6 (current version is 4) is going to 
really kick ass. From what I understand it has a superset of BeFS's 
functionality.

You'll be able to do things like (syntax isn't actually decided yet):

bash$ ls '[subject/[illegal strike] to/elves from/santa ultimatum]'

Which would list any files you have which have a subject attribute containing 
sub-attributes illegal and strike, the attribute ultimatum, etc. (Your email 
program and the filesystem would each automatically generate pieces of these 
attribute trees.) Technically they aren't "attributes", but instead part of 
the filename itself--it's just that filenames would now have two operators, 
'/' (ordering) and '[ ... ]' (grouping), instead of only one, '/'.

Regardless, while I very much like your idea on principle, I do think it's an 
idea whose time has not yet come. That doesn't mean we can't think about how 
to do it when it's time does come, however. ;-)

Evan


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-06-05  9:17 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
2003-06-05  9:50       ` Marko Mikulicic
2003-06-05  9:17     ` Evan Powers [this message]
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=200306050517.38134.powers.161@osu.edu \
    --to=powers.161@osu.edu \
    --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