From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] WeeChat -- Fast, light and extensible chat client
Date: Thu, 31 Oct 2013 23:47:00 -0000 [thread overview]
Message-ID: <5272EC10.60105@users.sourceforge.net> (raw)
In-Reply-To: <20131018164013.GM23477@calimero.vinschen.de>
On 2013-10-18 11:40, Corinna Vinschen wrote:
> On Oct 18 16:54, Sebastien wrote:
>> And I understood why they were missing: my locale is french under cygwin
>> (LANG=fr_FR), and the cygport tool is grepping output of "objdump -p" for the
>> text "DLL Name:" (file pkg_info.cygpart in cygport sources). When your locale is
>> not english, this text is translated (in french I have: "Nom DLL:").
>>
>> So if I run cygport with this command:
>>
>> cygport weechat-0.4.2-1.cygport package
>>
>> I have nothing in "requires" field.
>>
>> Instead I have to run:
>>
>> LANG=C cygport weechat-0.4.2-1.cygport package
>>
>> which gives all dependencies in the "requires" field.
>>
>> I think it is a bug in cygport tool.
>> Or at least, if you consider it's not a bug, it should be mentioned in the help
>> that the tool must be run with an english locale (or LANG=C). Anyway, I think it
>> would be better to fix that, so that other users will not spent time like me to
>> understand why the "requires" field is empty!
>
> Yaakov, any comment?
This should be fixed in git master, commit 50cdfcd; running cygport
itself with LANG=C should NOT be necessary.
(BTW, I'm willing to consider localizing cygport itself if there are
interested translators.)
Yaakov
next prev parent reply other threads:[~2013-10-31 23:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 16:34 Sebastien Helleu
2013-10-18 8:22 ` Corinna Vinschen
2013-10-18 14:54 ` Sebastien Helleu
2013-10-18 16:40 ` Corinna Vinschen
2013-10-18 17:55 ` Christopher Faylor
2013-10-21 6:26 ` Jan Nieuwenhuizen
2013-10-21 6:58 ` Yaakov (Cygwin/X)
2013-10-21 7:29 ` Sebastien Helleu
2013-10-31 23:47 ` Yaakov (Cygwin/X) [this message]
2013-11-01 8:32 ` Sebastien Helleu
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=5272EC10.60105@users.sourceforge.net \
--to=yselkowitz@users.sourceforge.net \
--cc=cygwin-apps@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).