Re: Re: preview-latex 0.9 released...

David Kastrup wrote:
> > If $prefix is NONE, it is set to $ac_default_prefix now. May I sugges=
t
> >
> > AC_DEFUN(EMACS_SET_PREFIX,[
> >   if test "${prefix}" =3D NONE -o -z "${prefix}"; then
> >     AC_MSG_CHECKING([for prefix of $EMACS_FLAVOR])
> >     EMACS_LISP(prefix,[(expand-file-name \"..\" invocation-directory)=
])
> >     AC_MSG_RESULT([$prefix])
> >   fi
> > ])
>=20
> It's not really an idea I'm overly comfortable with.  Because it means
> that using an Emacs in a nonstandard location will stop making an
> installation work on an otherwise standard system.

In essence, the old configure script set prefix locally for the
emacs-lisp test and used another prefix for the tex tests. Some time
ago you decided to set the prefix script-wide. I am not overly
satisfied with this choice.

> In particular, the TeX directories are also looked for
> prefix-relative.

Yes. And here, the prefixes are different. The code I had written
handled this gracefully. This does not work anymore. There has been no
reports on the list on strange install problems with the old code that
I can recall. Perhaps you have got them privately. Anyway, I really
like the new code better, and I think this can be fixed.

> > Well, you do check that it is the last in the path string.
>=20
> I do?  Since when?

I cannot look at the code at the moment, but I got the impression that
an entry in the first list needed to be last in the path found for the
path to be accepted. Perhaps this was wrong?

> Anyway, a warning to all people: I have decided that the current
> situation appears to hold up people fixing what I have started.  The
> active participation of preview-latex developers on the CVS is mostly
> restricted to myself at the moment, of course not counting the dvipng
> involvement.
>=20
> I want our AUCTeX developers to be able to take a pick at what is
> intended to become the procedure for AUCTeX, anyway.
>=20
> So I am packaging the nightly snapshot of preview-latex this night and
> am sending it to the Savannah hackers.  I don't know how long it will
> take them to place it in the archive: I have not preannounced
> anything.  I will tell them to place everything for now, and that
> dvipng is possibly intended as a separate non-GNU project on
> Savannah.  If doing otherwise would cause work, I don't mind if the
> anonymous and web access reflect dvipng until this has been decided
> and sorted out and dvipng either moved or removed on Savannah.

dvipng is a non-GNU project already at Savannah, and I would not mind
if the dvipng portion of the preview-latex CVS tree got put in the CVS
repository of the dvipng project. Not that I'd mind having it inside
the AUCTeX cvs tree, but perhaps there will be less confusion this way.

> _If_ Jan-=C5ke decides to switch (he has been pondering it at one time)=
,
> it will probably make things a tiny bit easier.=20

I take it you mean switch to Savannah, right?

> If he doesn't,
> removing dvipng again will not make much work.  I'll ask to get
> everything placed into a subdirectory "preview" for starters.

Perhaps you could ask if dvipng could be put in its own repository?

After this is finished, the people that devel access to dvipng will
need to drop me a note.

/J=C5


--=20
C Code. C code run. Run, code, run! (please?)


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click