public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joseph Hardin <jhlazer@charter.net>
To: Michael Kohl <citizen428@cargal.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] (FS) Attributes for Ebuilds?
Date: Thu, 5 Jun 2003 01:02:35 -0600	[thread overview]
Message-ID: <AF4E13B6-9723-11D7-B88A-000A95686F0A@charter.net> (raw)
In-Reply-To: <20030605144733.317a7b1c.citizen428@cargal.org>

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. Or just include it as a comment in the 
.ebuilds and build a tool to search through these comment strings and 
write its own as u add categories?

								Joe Hardin

On Thursday, Jun 5, 2003, at 00:47 America/Denver, Michael Kohl wrote:

> Hi all!
>
> Following all the recent discussion about categories in the Portage
> tree, having packages in several categories at once, defining key words
> for packages to ease finding a similar package an idea came to my mind.
>
> Would it be possible to use filesystem attributes for Ebuilds (of 
> course
> only if the FS supports this, maybe a local useflag can do the trick)?
> This would allow users to build categories "on the fly" using a kind of
> live query mechanism.
>
> People familiar with BeFS most probably know what I'm talking about, 
> for
> anyone else just a little info:
>
> This would allow to store metadata in text form for each ebuild as a
> filesystem attribute. Therefore your filesystem kind of acts like a
> database. Using this mechanism you also could add your own attributes
> (e.g. "try_this" for ebuilds you're interested in testing sometime) and
> then list all ebuilds having this attribute.
>
> Also the setup part of an Ebuild could set an attribute like 
> "installed"
> in pkg_postinst, so it would be even easier to find all the packages
> installed on your system. Using live queries (e.g. in a nice GUI) this
> list would change immediately after you emerged a new package. Also
> finding applications similar to each other would be quite easy, as you
> can store quite a lot of metadata (e.g. mp3, ogg, media, player, etc.
> for the xmms ebuild). Sure this could be done in various other ways, 
> but
> using FS attributes just sounds like a good way of doing it.
>
> Comments (especially about the various FS and their usefullnes for this
> purpose), ideas, thoughts anyone?
>
> Michael
>
> P.S. Sorry, the thoughts in this mail aren't all that well organized or
> explained, I'm not feeling to good today...
>
> -- 
> www.cargal.org
> GnuPG-key-ID: 0x90CA09E3
> Jabber-ID: citizen428 [at] cargal [dot] org
> Registered Linux User #278726
> <mime-attachment>


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-06-05  7:02 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 [this message]
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
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=AF4E13B6-9723-11D7-B88A-000A95686F0A@charter.net \
    --to=jhlazer@charter.net \
    --cc=citizen428@cargal.org \
    --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