size of release sets (was Re: [Clipart] Open Clip Art Library - Release 0.06)
jon at rejon.org
Tue Aug 31 18:49:09 PDT 2004
Yes, this would be a good task for someone to take on. Like nightly
tarballs/packages that people can download/update their library to
everyday. I guess we could add an apt/rpm repository that people could
access to update to the newest clip art. Thoughts?
Bryce, what do you think? How could this relate to DMS work?
Eventually, to offer a web service where synchronization and various
front-ends to our system will be the penultimate. Bryce's DMS work will
fit into this nicely.
On Tue, 2004-08-31 at 18:19, Jeremy C. Reed wrote:
> On Tue, 31 Aug 2004, Jon Phillips wrote:
> > However, we have to remember that we are a nonstandard OSS project in
> > that we offer constantly change/updating content. Normal OSS projects
> > release stable builds as releases, but our up-to-the minute repository
> > is probably the more preferred method for disseminating content. Thus,
> > ways we and make packages on the fly would be very useful. See the
> > microsoft clip art website to see a great example of how to deal with
> > packaging/baskets for clipsrt.
> I agree. I should have said we should have premade tarballs "in addition"
> to the dynamic downloads.
> But I also think that some operating system users would like to have their
> native packaging tools provide the clipart.
> apt-get update ; apt-get upgrade # and you have new clip art :)
> > > It would be useful in the future if there were premade tarballs so to save
> > > time downloading (and to use less resources on the download server) and so
> > > the checksums for the files are consistent.
> Jeremy C. Reed
> BSD News, BSD tutorials, BSD links
> clipart mailing list
> clipart at freedesktop.org
jon at rejon.org
Open Clip Art Library (www.openclipart.org)
CVS Book (http://cvsbook.ucsd.edu/)
Scale Journal (http://scale.ucsd.edu/)
More information about the clipart