[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LilyPond 1.3.148

From: Mats Bengtsson
Subject: Re: LilyPond 1.3.148
Date: Thu, 19 Apr 2001 14:47:30 +0200

> What could be done, I think, should be to download the comp-
> lete MiKTeX package,  and launch the installation after the
> Lilypond setup is done. Of course, Jan's solution seems mor-
> e plausible if those "tarballs" are really a lot less heavy
> than the full 25 Mb MiKTeX 2.0 package. It's obvious why so-
> mebody using a modem line, and wanting only to use Lilypond
> would prefer such a solution. If really that's a problem, w-
> hy can't an additional package, that installs every other c-
> omponent of MiKTeX that wasn't installed during the Lilypon-
> d setup be provided?

Are there any problems to launch an external installation program
during the Lilypond setup? You don't want to wait til after the 
setup, since the Lilypond setup has to(?) know where the other
packages are located.

MiKTeX is modular today, see
You only need the Level 1 packages.

> > > The bad news is that it doesn't really work yet, it seems that python
> > > needs more registry entries to know that it's running on windows.  Or
> > > maybe it's a different problem altogether.  Lily,tex,yap,gsview seems
> > > ok, but ly2dvi barfs.
> The first solution that comes to (my) mind, would be to hav-
> e the bash installation script generate an exported registr-
> y value file (the *.reg managed by Regedit) and have it ins-
> ert all needed values for Python into the registry. It does-
> n't require much work. I attached a file that should set ev-
> ery key necessary to Python, but I haven't any way of testi-
> ng it.  I'll explain what the paths are, though I doubt you
> need help.

I wouldn't want to support such a thing, that's why I propose
to use the standard installation procedures whenever possible.
Of course, if you volounteer, it'd be great. 


reply via email to

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