From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: 64bit lapack-3.7.0-1.tar.xz - Empty
Date: Fri, 07 Apr 2017 11:44:00 -0000 [thread overview]
Message-ID: <703af550-db59-326a-83bd-7407fb752612@dronecode.org.uk> (raw)
In-Reply-To: <2aa7094b-6fbc-c981-c20a-4270c1d173bd@cygwin.com>
On 04/04/2017 18:19, Yaakov Selkowitz wrote:
> On 2017-04-04 12:03, cyg Simple wrote:
>> On 4/4/2017 9:04 AM, Marco Atzeri wrote:
>>> On 04/04/2017 14:43, cyg Simple wrote:
>>>>
>>>> Exactly but the binary install of lapack should require liblapack-devel
>>>> and liblapack0.
>>>
>>> I disagree. It will not happen for my packages
>>
>> What's the hardship that causes you to make such a bold statement? You
>> upload the same number of files, the only difference is telling setup
>> that the package has dependencies.
>
> It's not a question of hardship, there is simply no need for it.
>
> Marco, you can simply remove lapack from PKG_NAMES in order to hide it
> in setup.
It's on my TODO list for calm to perhaps have it discard binary packages
which are 1/ empty and 2/ have no dependencies, to avoid this kind of
confusion.
Historically, this has also caused problems where people have mistakenly
specified this empty package as a dependency (e.g. written lapack where
they should have written liblapack0)
--
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:[~2017-04-07 11:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 14:52 cyg Simple
2017-04-03 15:00 ` Marco Atzeri
2017-04-03 15:07 ` cyg Simple
2017-04-03 15:44 ` Marco Atzeri
2017-04-04 12:43 ` cyg Simple
2017-04-04 13:04 ` Marco Atzeri
2017-04-04 17:03 ` cyg Simple
2017-04-04 17:19 ` Yaakov Selkowitz
2017-04-04 19:17 ` Marco Atzeri
2017-04-05 17:10 ` cyg Simple
2017-04-07 11:44 ` Jon Turney [this message]
2017-04-07 13:43 ` cyg Simple
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=703af550-db59-326a-83bd-7407fb752612@dronecode.org.uk \
--to=jon.turney@dronecode.org.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).