From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Re: Libguile17 dependency issue - attention maintainer
Date: Sun, 12 Apr 2015 13:11:00 -0000 [thread overview]
Message-ID: <552A6ED2.20503@tiscali.co.uk> (raw)
In-Reply-To: <552A42DC.9080703@gmail.com>
On 12/04/15 11:03, Marco Atzeri wrote:
> On 2/21/2015 12:19 AM, David Stacey wrote:
>> On 20/02/15 15:42, Corinna Vinschen wrote:
>>> unfortunately it turns out that our guile (and lilypond) maintainer has
>>> left us, so the packages are orphaned. Jan's last version of guile was
>>> 1.8.7-2 for 32 bit.
>>>
>>> Does anybody have fun to take over maintainership of guile or lilypond?
>>
>> First, let me say that I have no intention of maintaining lilypond - I
>> am aware that even replying to this e-mail puts me in danger of
>> acquiring another couple of packages ;-) I absolutely love lilypond and
>> would like it to stay within Cygwin if at all possible, but I don't have
>> the time right now to take on a package that is going to be a little
>> problematic.
>>
>> I had a go at building lilypond for x86_64 about 18 months ago, but
>> didn't get very far. I managed to produce an executable, but 'make doc'
>> and 'make check' both failed, so I didn't have any confidence in the
>> binary produced. My need for a working lilypond exceeded the tinkering
>> time available, so I just used Fedora.
>>
>> I've tidied up the cygport file this evening, and this (along with a
>> small patch) is attached. Hopefully this will be a starting point for a
>> prospective maintainer with the time to do it justice.
>>
>> Dave.
>
> Thanks Dave,
> for the starting point.
> I used that as base for the 64 bit package just released.
>
> Removing the cygwin specific usage of
> cygwin_conv_to_posix_path / cygwin_conv_path
> did the work. Make check passed on 64bit, and make doc fails
> on a corner case, most of the HTML documentation was built.
Well done - you've already got further than I managed. I have a soft
spot for lilypond, so I'm really pleased that you've adopted it - I'd
hate to see it removed from Cygwin. Next time I update my 64-bit
installation I'll give it a test.
Dave.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-04-12 13:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 1:00 [ANNOUNCEMENT] Updated: make-4.1-1 Ti Strga
2015-02-20 15:42 ` Franz Sirl
2015-02-20 16:20 ` Libguile17 dependency issue - attention maintainer Marco Atzeri
2015-02-20 16:21 ` Cosimo Lupo
2015-02-20 16:42 ` Marco Atzeri
2015-02-20 17:24 ` Achim Gratz
2015-02-20 19:08 ` Yaakov Selkowitz
2015-02-20 16:24 ` Corinna Vinschen
2015-02-20 16:41 ` Marco Atzeri
2015-02-20 17:05 ` Corinna Vinschen
2015-02-21 0:50 ` David Stacey
2015-04-12 10:03 ` Marco Atzeri
2015-04-12 13:11 ` David Stacey [this message]
2015-04-12 20:17 ` David Stacey
2015-04-12 20:39 ` Eliot Moss
2015-04-12 21:45 ` Marco Atzeri
2015-04-13 9:56 ` Lilypond Marco Atzeri
2015-04-13 11:54 ` Lilypond Eliot Moss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=552A6ED2.20503@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).