Hi Paul,

Firstly sorry if I sounded rude and ungrateful. That wasn't my intention.

On 19 Oct 2004, at 11:22, P.C.Callaghan wrote:
James,

You are right on the point about distinguishing stable and experimental
releases - this seems quite important, given recent events. Any volunteers
for this?


Ideally we should also have some kind of automatic basic testing as well,
to prevent obvious breakages. Volunteers? There are fragments lying around.

This sounds like a good idea.

many existing and potential users like things to work out of the box
(think professors and undergraduates...).

What we have at the moment doesn't work out-of-the-box. We need something that once installed does what's expected: gets put in start menu; you can drag it into applications; appears miraculously in your path; or whatever.


But I disagree (still) about "why save people 10 mins of compiling etc" -

What I was really trying to say is that is /all/ we are saving people at the moment. We are providing something that works in-place, providing all its dependencies are met, we are just doing the first(only) stage of the build from source for them. Something that conforms to:


./configure <-- this would have picked up the last two build problems on this list i think.
make
make install <-- we need this too I think - "I've built it. Now what?". Things need to be installed in /usr/local/ or somewhere like that.


would be good I think.

Maybe an rpm and a deb too?

Note there is only one cron job, which makes the Solaris version from
clean; then it bundles the most recent linux and windows binaries into
relevant packages.  (We could also make the Linux binary from scratch -
volunteers?) And I don't see how/why adding relatively minor platforms
(outside the four we've got) means we shouldn't bother with automating
the main platforms. That doesn't seem sensible.

Ok, as much automation as possible is of course the right thing to do.

What do you mean by "sensible installer" though? The windows and unix
packages (should) work by a single entry point which sets all relevant
flags. What more do we need?

On windows I was referring to something that uses Windows Installer and produces an msi file. It then adds things to the start menu and can be un-installed. When I've installed epigram in our labs I've had to make these bits manually. Location of dependencies (xemacs at the moment) are also an issue here. Same sort of thing for Apple.


Another one for the "implementors mtg"?

Think I should probably buy the first round!

And in answer to the 'volunteers?' I think I've probably comprehensively volunteered myself.

Regards,

James



Reply via email to