[Debtags-devel] where to post future data updates

[Enrico Zini]

--+QahgC5+KEYLbs62
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline

On Sat, Jul 31, 2004 at 03:02:01PM +0000, Thaddeus H. Black wrote:

> From where shall a user get a data update?

I suggest you ship a base debram.txt file in /usr/share/debram/ together with
the debram package, then you provide some facility for downloading new
versions of the archive and storing them in /var/lib/debram.  The
application could then check if the two files (the one in /usr/share and
the one in /var/lib) are present.  If they are, it should take the newer
one; if only one is present, they should take that.

Since you ship a debram.txt together with your package, a database, even
if old, will always be present, and debram will be guaranteed to work.

I don't think it's a problem to use alioth for downloading this: it's
totally a service for Debian, and that's what Alioth is for.  You could
even setup a subversion post-commit hook like I did with the debtags
webspace (or you could use the debtags webspace altogether), so that
when you commit a change to debram.txt, the web copy gets automatically
updated.


Ciao,

Enrico

--
GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini <enrico@debian.org>

--+QahgC5+KEYLbs62
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBHWQO9LSwzHl+v6sRAhWnAJ90zCtLO0VnXWo06kSihyiQYlNF/wCgjDku
MsKj0vy5yu9ToM7SaqpilRU=
=TSMx
-----END PGP SIGNATURE-----

--+QahgC5+KEYLbs62--