On Thu, 12 Jan 2012 11:16:21 -0800, tony mancill wrote: > On 01/12/2012 04:31 AM, David Paleino wrote: > > On Thu, 12 Jan 2012 12:51:41 +0100, Francesco P. Lovergine wrote: > > > >> On Fri, Jan 06, 2012 at 11:34:41AM +0100, David Paleino wrote: > >>> On Fri, 30 Dec 2011 11:59:55 +0100, David Paleino wrote: > >>> > >>>> Hello people, > >>>> I intend to package some shapefiles [..] > >> > >> Once upon a time... someone proposed data.debian.org for packaging such > >> kind of information. Still in a limbo AFAIK. That said, I see no problems > >> in packaging relevant data (but what about size ?). > > > > Do you mean archive-size, or installed-size? If the latter, I see no > > problems: the only overhead would be the Debian-specific files (copyright, > > changelog.Debian, and so on). If you meant archive-size, those are usually > > arch:all packages, and I'm not aware of any "size policy" for data packages. > > Just think at those *-data for games :) > > What would be nice about data.debian.org (or similar) would be that the > data files could be volatile - i.e. not tied to a specific release > throughout the release cycle. That's doable too, but it'd require a good amount of work and well-thinking. We could start providing "control files" in pkg-grass.alioth.debian.org, and make some scripts to grab these. Something similar to flashplugin-nonfree, i.e. the user has to run (hypotetical commands): $ grab-shapefile somename And the script will connect to some web space (pkg-grass.a.d.o?), grab the shapefiles, and do some magic to handle them (we don't want shapefiles scattered throughout the filesystem, do we?) Surely pkg-grass.a.d.o could someday become data.d.o, but I don't really have the time to handle it -- nor really to handle the example above. With the current spare time I have, I'd be only able to provide "traditional packages". Kindly, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 ----|---- http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
Attachment:
signature.asc
Description: PGP signature