public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] libsass v3.3.6
Date: Thu, 09 Jun 2016 09:37:00 -0000	[thread overview]
Message-ID: <fb3b2b92-cc75-0fb3-ad92-04a663976c33@gmail.com> (raw)
In-Reply-To: <CABKfh3z2CCqoJrb2zXKWhfzJ4Nfk=mWWx_WL-C=JJxsjeWqipQ@mail.gmail.com>

On 08/06/2016 00:17, Marcos Vives Del Sol wrote:
> On 07/06/2016 11:49, Achim Gratz wrote:
>> Based on the way configure is supposed to be working it seems that either
>> the tarball you're using is incomplete (did you use a Git snapshot?) or
>> they forgot to package the VERSION file.
> Yes. It's a Git snapshot indeed, as generated by GitHub (using the
> built-in release functionality), and they forgot to create the VERSION
> file after creating the package. The .tar.gz is 1:1 from
> https://github.com/sass/libsass/releases/tag/3.3.6.
>
> 2016-06-07 12:02 GMT+02:00 Marco Atzeri:
>> As VERSION doesn't exist is is not created in the
>> src root (libsass-3.3.6-1.x86_64/src/libsass-3.3.6)
>> but two level upper:
>>
> ...
>>
>> It is a side unwanted effect of the smart patching.
>> If you want to create it, you should rewrite it as:
> Thanks! Fixed: http://mural.uv.es/videlsol/libsass/
>

I added libsass to the package list.
Feel free to upload

Regards
Marco

      parent reply	other threads:[~2016-06-09  9:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 15:10 Marcos Vives Del Sol
2016-06-06 10:09 ` Marco Atzeri
2016-06-06 16:46   ` Marcos Vives Del Sol
2016-06-06 17:07     ` Achim Gratz
2016-06-07  9:36       ` Marcos Vives Del Sol
2016-06-07  9:49         ` Achim Gratz
2016-06-07 10:02           ` Marco Atzeri
2016-06-07 22:18             ` Marcos Vives Del Sol
2016-06-08  5:46               ` Achim Gratz
2016-06-08  8:02                 ` Marcos Vives Del Sol
2016-06-08 18:55                   ` Achim Gratz
2016-06-09  9:37               ` Marco Atzeri [this message]

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=fb3b2b92-cc75-0fb3-ad92-04a663976c33@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).