Comment #28 on issue 1933 by mts...@gmail.com: Lilypond-book requires
msvcrt again
http://code.google.com/p/lilypond/issues/detail?id=1933
PS. I know that you're confused and irritated about the whole thing, but
this is only one small part of dealing with releases. I suffered through
over a hundred hours of this crap in 2009. We simply do not have experts
in this kind of stuff actively involved in lilypond. There are three
options:
1. give up and abandon the whole project. (which is looking increasingly
attractive to me)
Don't do that!!
2. become an expert in this field yourself.
I don't have the time.
3. take over more tasks from me so that I can suffer through this process
instead of you.
I wouldn't mind doing this, as long as they're tasks I can handle.
I understand that you're dedicated to releasing LilyPond with Python, and
as you have much more experience in the domain, I trust you that it's worth
it. What seems difficult to me is exactly what seems difficult to you: we
are maintaining a feature for which we have no current developer who is an
expert and who can give your time. Furthermore, the feature is easily
gettable elsewhere (downloading Python from website). I trust that there
are 100s of hours of other build-related stuff that you need to do, which
is precisely why I thought it'd be good to get rid of whatever is
non-essential until we get someone on the development team that is into
this sorta thing.
Both of us are imagining this from a worth cost perspective. I'm having
trouble imaging that the worth of a packaged Python is greater than or
equal to the worth of spending developer resources on understanding it and
fixing it every time something goes wrong. However, I defer to your
knowledge on it - I just want this opinion to be out there because I think
that it's always important to fully consider the value of pruning projets
with the same seriousness that we consider growing them.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
