public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>,
	"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: New version of GLM package?
Date: Sun, 20 Dec 2020 11:55:43 +0100	[thread overview]
Message-ID: <5522d0a1-aa4c-50d2-4132-18435ef48d00@gmail.com> (raw)
In-Reply-To: <e77a06df-f1b8-6ae9-b808-592c54784ab2@t-online.de>

back on the mailing list

On 20.12.2020 00:23, Hans-Bernhard Bröker wrote:
> Am 19.12.2020 um 19:21 schrieb Marco Atzeri via Cygwin:
> 
>> for what I can see upstream has completely removed the install
>> section from the cmake files on 0.9.9.8 .
>>
>> unclear why they performed such issue.
> 
> Possibly because there isn't all that much to install for a "library" 
> that does not actually contain any compiled files, because it consists 
> of nothing but inlined templates in header files.
> 
> I.e. the binary package would just be a subset of the source in a 
> different place.
> 
> They seem to assume that the cmake script snippet they offer is 
> sufficient to make the package count as "installed", because that (with 
> an environment variable on top) allows the package to be found by CMake 
> packages.  The canonical method would probably be a CPack package.

Hi Hans,

I have impression debian is using such assumption and copy just the
files in the proper place.
It is annoying anyway.

The fact that the github repository seems to not have the "issues"
is another annoying problem of this package.

Regards
Marco






  parent reply	other threads:[~2020-12-20 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 13:19 Carlo B.
2020-12-17 14:13 ` Marco Atzeri
2020-12-19 18:21   ` Marco Atzeri
     [not found]     ` <e77a06df-f1b8-6ae9-b808-592c54784ab2@t-online.de>
2020-12-20 10:55       ` Marco Atzeri [this message]
2020-12-20 11:58         ` Carlo B.
2020-12-20 13:31           ` Marco Atzeri
2020-12-21 10:27             ` Carlo B.

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=5522d0a1-aa4c-50d2-4132-18435ef48d00@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=HBBroeker@t-online.de \
    --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).