public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] libsass v3.3.6
Date: Wed, 08 Jun 2016 18:55:00 -0000	[thread overview]
Message-ID: <871t47v7bn.fsf@Rainer.invalid> (raw)
In-Reply-To: <CABKfh3zeuxvqUGZf3wLC2aAWFhazzNkokzJxSRgDenE1+qVrVg@mail.gmail.com>	(Marcos Vives Del Sol's message of "Wed, 8 Jun 2016 10:02:02 +0200")

Marcos Vives Del Sol writes:
> 2016-06-08 7:46 GMT+02:00 Achim Gratz:
>> They didn't forget anything, you are just not using a release tarball.
>> In that case you are expected to either build from a proper Git checkout
>> or run the release preparations yourself before configure.
> I am compiling a release tarball, as I've already said:
> https://github.com/sass/libsass/archive/3.3.6.tar.gz. That's the
> official tarball.

I've looked at their Makefile and documentation and it appears that
upstream don't do any preparation of any sorts for a release.  The
"release tarballs" are just snapshots for the release tag that don't
contain the extra file(s) that would actually be required based on the
rules in configure and the Makefile.

> Anything else to fix before it's GTG?

You might want to consider building from a Git checkout instead of the
tarball.  It seems that this is the recommended way to build and the
other build venues are obviously more or less untested these days.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

  reply	other threads:[~2016-06-08 18:55 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 [this message]
2016-06-09  9:37               ` Marco Atzeri

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=871t47v7bn.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).