Crossfire Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: eutl updates?



On Thu, 27 Apr 1995, Eric_Arnold Anderson wrote:

> I'm going to be sending out a new release real soon now.  I've done
> ports to solaris 2.[34], alphas, decs, hp's.  I'm currently getting
> nice configuration stuff done.  (Not imake)

Please do support in configuration support changing compilers,
flags etc. In a way the compiler can be changed into c++
easily.

>  > The separation of files seems to be now quite developmental.
>  > If it can be considered the library is in quite stable state,
>  > means no big service additions (porting although), the files
>  > could be collected into one directory, when writing Imakefile
>  > for it is simple.
> It's probably better to keep it separate from the crossfire 
> stuff.  I'm going to be using it for many other things (in fact
> I already am), and so keeping the distributions separate will allow
> improvements to eutl to not force a re-release of crossfire.
> Anyway, eutl is released under a different copyright.  I can't 
> remember right now if you can put a GNU copyleft on it.

I mean this to restructure directories internal in package
to provide easier compilation, installation etc. (if ever
needed). Indeed there are no reason to mix eutl with e.g.
common part, because crossfire depends from eutl, but eutl
does not depend from crossfire.

The other question is distribution. The eutl could be
distributed among the crossfire as a subdirectory (as
there is Cnv in crossedit, that depends from it, but
Cnv is indeed independed package for message boxes,
file selections etc.). Or the eutl could be distributed
as a own packet, as it's now, and it seems you manage
the distribution. 

<A HREF="http://www.lut.fi/~hevi/">Petri.Heinila@lut.fi</A>