Complete.Org: Mailing Lists: Archives: freeciv-dev: February 2002:
[Freeciv-Dev] Re: Suggestions
Home

[Freeciv-Dev] Re: Suggestions

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: rf13@xxxxxxxxxxxxxxxxxxxxxx
Cc: Eric E Moore <e.e.moore@xxxxxxxxxxxxxxx>, freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: Suggestions
From: Jules Bean <jules@xxxxxxxxxxxxxxx>
Date: Tue, 5 Feb 2002 12:00:34 +0000

On Mon, Feb 04, 2002 at 11:09:55PM +0100, Raimar Falke wrote:
> On Mon, Feb 04, 2002 at 09:17:06PM +0000, Eric E Moore wrote:
> > Raimar Falke <hawk@xxxxxxxxxxxxxxxxxxxxxxx> writes:
> > 
> > > As a maintainer: 
> > >  - costs: some now and some in the future (patching for example)
> > 
> > could store images as base-64 encoded PNG's..  probably still smaller
> > than a XBM.  Might introduce some additional library dependency (or
> > just code to un-base-64 it).  Could do the same for wavs, or any other
> > binary file.  Or could make something to un base-64 it a build
> > dependency, and just use base-64 in CVS.
> 
> Suppose you have two files: foo.png and foo.png.base64. A person has
> changed foo.png and want to send the changes to freeciv-dev. So
> foo.png.base64 has to be created from foo.png. If on the other side I
> got a patch which changes foo.png.base64 I want that foo.png is
> updated. So you have to have two distinct conversation. One of the
> sides has to do an extra conversion. This would be similar to autoconf
> (if you change configure.in you have to run autoconf to get an
> effect).

CVS can be told to do this automatically, I think. Not sure.  It can
do some preprocessing.

But why bother?  CVS handles binary files, it just doesn't transmit
diffs, it transmits the whole thing.  Is that a problem?

Jules



[Prev in Thread] Current Thread [Next in Thread]