> >I've incorporated the OpenPoplog Win 2000 stuff to
see
> >if there's any noticeable difference.
> >
>
> The really useful file would be your *.iss file for
driving InnoSetup.
> My version is quite complicated because I'm trying
to support
> half-a-dozen different installation options, e.g.
"All Platforms",
> "Windows Full", "Binaries only", etc. From an
administration point of
> view, once this is set up, I think it will be easier
to maintain.
Yes. My version is very simple (in fact, it may not
do all the right things, as I'm not as familiar with
Poplog as you). I'm attaching the script for your
amusement. :-)
> I have just checked in my version of the script,
called
> poplog15.54.iss.
> You should find it in the repository at
/CVSROOT/openpoplog/poplog/build.
I'll compare the two and see if I can improve my
simple script at all.
> >I'm interested in how to bootstrap. I use Windows
at
> >work, but Debian at home and I'd like to get a
> >smoother install (i.e., more integrated) for
Debian.
>(I'm not sure if, by "smoother install for Debian",
you mean you want to
> use the same download to install the Windows and
Debian downloads, or if
> you just mean that you want a better-scripted Debian
install?)
The latter. Here are the problems I have with the
current Linux tarballs:
1. They aren't built against current libraries, so
you have to install old libraries like termcat and
libc5.
2. Poplog does not get installed in the right places
according to the Linux File System Standard. Ideally
the man pages would go into the system manpage
directory, Binaries would go in /usr/bin, etc.
There's leeway in this, obviously, but it would make
integrating with Emacs and other tools easier if
things could be found in "expected" places.
3. GTK or QT would be preferable to Motif (this is a
longer-term goal).
4. A GNUstep binding might be a better use of time,
since this would provide a Linux and a Mac OS
X-compatible GUI toolset.
> It is my aim that the code base at SourceForge
should be a consolidated
> code base from which we can pull off distributions
for any supported
> platform.
I agree with that goal.
> I may decide that Newcastle is too far away, and I'd
rather
> spend a few weeks alternately playing with Poplog
and integrating some
> refactoring tools into the VB IDE before I'm next
asked to implement VB
> programs against a constantly mutating
specification, while watching
> the
> Chaffinches playing in the garden. Since demand for
IT services seems to
> have picked up, this may be a risk worth taking.
Good luck, either way.
Thanks,
-Brent
|