Date: Tue, 26 Mar 2002 19:15:28 +0100 From: Roman Neuhauser <neuhauser@mobil.cz> To: Dan Langille <dan@langille.org> Cc: freebsd-questions@freebsd.org Subject: Re: XML interface to CVS Message-ID: <20020326181528.GS389@roman.mobil.cz> In-Reply-To: <20020326152301.38D7A3F28@bast.unixathome.org> References: <20020326111149.GA389@roman.mobil.cz> <20020326152301.38D7A3F28@bast.unixathome.org>
index | next in thread | previous in thread | raw e-mail
> From: "Dan Langille" <dan@langille.org>
> To: Roman Neuhauser <neuhauser@mobil.cz>
> Date: Tue, 26 Mar 2002 10:22:59 -0500
> Subject: Re: XML interface to CVS
> Cc: freebsd-questions@freebsd.org
>
> On 26 Mar 2002 at 16:01, Roman Neuhauser wrote:
>
> > Ah, I just read the article on daemon news, and now I see you
> > actually *do* want XML... Sorry about that.
>
> Which article on daemon news?
http://daily.daemonnews.org/view_story.php3?story_id=2548
> > Anyway, could you shed
> > some light on the "any source tree of any type" thing? What does
> > that mean in regard to fp2?
>
> I'll put in a bit of background and future goals first. Your questions
> should be answered somewhere in the next few paragraphs. If it doesn't,
> tell me.
> The basic change has been the underlying database structure. It's now
> PostgreSQL and was mySQL. The main reason for the change was stored
> procedures and triggers [3] which allowed for a recursive design.
How is the recursion used? I guess I wouldn't have to ask this
question if I knew what FP does for the ports tree. :) (Not that I
don't have a rough idea, but I don't know the internals.)
> This new structure will allow me to do for the whole source tree what
> FP does for the ports tree. This new project is called FreshSource
> [4]. With FS, you can place any file or directory on your watch
> list; in FP, you can only put a port on your watch list [which makes
> sense; it's only for the Ports tree].
>
> FreshPorts was designed for the FreeBSD ports tree, but the goal is to
> allow other port trees to use it as well. With FP2, we have moved to
> XML as the primary input. Each cvs-all message is converted to XML
> and then processed by FP2. This will greatly simplify the inclusion
> of other port trees.
>
> The FP2 database was populated by migrating data from FP1. However,
> the ideal population method would be directly from CVS, hence the
> query about an XML interface to CVS. It would also allow FP2 to query
> any CVS repository and populate itself.
Do you want to store old revisions in the FreshPorts database?
Example:
OpenBSD ports collection FP-site is started. Does it make any sense
to load the complete history of the tree when FP is a "remind me"
service?
Looks to me like it's not that useful...
I mean, it's quite nice to keep older revisions for some time, but I
don't really grok the need to load the complete history of a CVS
tree upon its registration.
Explanation?
> This feature would probably have a bigger effect on FreshSource than
> FreshPorts, but the capability would useful for both.
Again: do you want to store old revisions?
> [4] - http://www.FreshSource.org/
What's the $CVSROOT? :)
Other than that, given that this is a push service (the CVS server
pushes the info to the FP/FS server, and that pushes it to the
subscribers), what would be more useful is a script that you could
register in commit hook, and it'd pass the XML over to a FP/FS
"listener". HTTP POST, RPC, whatever...
Of course, the FP/FS service can just query the CVS server in
scheduled intervals, or parse emails...
XML is indeed useful in this situation, because it allows for for
quite a variety of revision-control systems: one could write an app
to get the info out of a Perforce repo, or a SVN one...
--
FreeBSD 4.4-STABLE
4:54PM up 2 days, 40 mins, 12 users, load averages: 0.04, 0.10, 0.07
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020326181528.GS389>