Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Oct 1996 09:16:20 -0500 (EST)
From:      John Fieber <jfieber@indiana.edu>
To:        "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc:        ports@freebsd.org
Subject:   Re: www.freebsd.org/ports/index.html 
Message-ID:  <Pine.BSI.3.95.961029090244.6405G-100000@fallout.campusview.indiana.edu>
In-Reply-To: <4042.846554473@time.cdrom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 28 Oct 1996, Jordan K. Hubbard wrote:

> > This is something I want very much, in addition to recently
> > changed/updated ports.  Unfortunately, the current mechanism for
> > generating the ports pages doesn't easily lend itself to such
> > features.  I have a little perl program that reads the ports
> > INDEX file and spits out HTML, but the INDEX file contains no
> 
> Hmmm.  This seems like one of those problems which might be better
> served through a cron job.  Why not simply cache the previous day's
> and previous week's INDEX files, doing a running diff each day which
> generates the HTML?

The problem is that a diff of the INDEX file is insufficient for
detecting changed ports.  (And personally I think this is at
least as important as flagging new ports.) The only way I can
think of for accurately representing changed ports is to dig
through the entire ports tree.  Of course, the easy solution
would be to assume that a change should only be flagged if it
represents an update version of a port, which will be reflected
in the INDEX file, as opposed to a tweak. But what if a tweak
fixes a critical bug such as a security hole?

As far as the creation date, that information only has to be put
in once and it *already is* standard practice to put it in. 
For new ports, there is no added cost, only a slight procedure
change.  For old ports, well, we can assume they are not new.

-john

== jfieber@indiana.edu ===========================================
== http://fallout.campusview.indiana.edu/~jfieber ================




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.95.961029090244.6405G-100000>