Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Apr 2004 19:22:26 -0400
From:      Garance A Drosihn <drosih@rpi.edu>
To:        Martin <nakal@web.de>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: Second "RFC" on pkg-data idea for ports
Message-ID:  <p06020421bca222e97833@[128.113.24.47]>
In-Reply-To: <1081896823.772.58.camel@klotz.local>
References:  <p0602040cbca10a7dbe52@[128.113.24.47]>	 <20040413121925.GB29867@voodoo.oberon.net>	 <p0602041abca1e49dde40@[128.113.24.47]> <407C4035.8020609@ciam.ru>	 <p0602041fbca1ff481e60@[128.113.24.47]> <1081896823.772.58.camel@klotz.local>

next in thread | previous in thread | raw e-mail | index | archive | help
At 12:53 AM +0200 4/14/04, Martin wrote:
>Am Tue, den 13.04.2004 schrieb Garance A Drosihn um 23:40:
>
>  > If someone has a better format, and a format which will be
>  > as easy for a simple program to process, I will be willing
>  > to try that format instead.  I am not too hung up on this
>  > specific format.
>
>I would personally like it to use XML. I'm developing a small
>application which is a kind of GUI for ports (works like a
>browser). It is very difficult to parse the Makefiles to find
>out which version number and which dependencies it has. Some
>versions (like KDE3) are just variables and I don't have an
>idea how to fetch them yet.

If it is easy for you to execute commands, then something
like:

/bin/make -f /usr/ports/shells/bash2/Makefile -V PORTVERSION

might give you the result you want.  But I do not know if
that will work for all ports.

>With a structured language like XML, it would make the
>parsing process for such utils like mine easier.

Well, one of my goals for this project is to make it easier
for others to write programs which do their own processing
of the ports-files.  I am a little worried about how long
it would take us (Darren and I) to figure out the right XML
format, and how to process it, but maybe we really need to
do that.

Would it be useful-enough if the pd-handling program
could spit out a true XML-formatted document, once we knew
what that was?  I realize this is rather lame, but it would
allow us to keep this key program pretty small and simple.

>  > That is what I was thinking of when I picked this specific
>  > format.  With this strict, limited format, it should be easy
>  > to write a program that can do all the processing we want
>  > to do (at least for now).
>
>Before using XML, you should really ask people who have an
>idea about both, ports and XML.

Well, at the moment I am *not* using XML...  :-)

Right now I'm just looking for feedback.  Thank you for
providing some more ideas for Darren and I to think about.

-- 
Garance Alistair Drosehn            =   gad@gilead.netel.rpi.edu
Senior Systems Programmer           or  gad@freebsd.org
Rensselaer Polytechnic Institute    or  drosih@rpi.edu



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06020421bca222e97833>