From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32644 invoked by uid 1002); 5 Jun 2003 07:02:20 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 16666 invoked from network); 5 Jun 2003 07:02:19 -0000 Date: Thu, 5 Jun 2003 01:02:35 -0600 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: gentoo-dev@gentoo.org To: Michael Kohl From: Joseph Hardin In-Reply-To: <20030605144733.317a7b1c.citizen428@cargal.org> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) Subject: Re: [gentoo-dev] (FS) Attributes for Ebuilds? X-Archives-Salt: b98cea36-2391-46a8-9252-793046ae0357 X-Archives-Hash: 4d7caf25a453a004ac82813f27eb32ff 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 > -- gentoo-dev@gentoo.org mailing list