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 sna
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
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 s
Marcos Vives Del Sol writes:
> 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 indee
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
On 07/06/2016 11:49, Achim Gratz wrote:
Marcos Vives Del Sol writes:
This script is called using m4_esyscmd_s from configure.ac line 6:
-
AC_INIT([libsass], m4_esyscmd_s([./version.sh]), [support@...])
-
to set the library version at compile time. Then configure
Marcos Vives Del Sol writes:
> This script is called using m4_esyscmd_s from configure.ac line 6:
> -
> AC_INIT([libsass], m4_esyscmd_s([./version.sh]), [support@...])
> -
> to set the library version at compile time. Then configure uses it to
> generate the version
2016-06-06 19:07 GMT+02:00 Achim Gratz :
> That file is created by configure, so patching it in anyway is still
> useless.
No. The file created by configure is version.h.
VERSION file later is employed by the version.sh script:
-
if test "x$LIBSASS_VERSION" = "x"; then
LIBSASS_VE
Marcos Vives Del Sol writes:
>> to avoid the useless creation of libsass-3.3.6-1.src.patch
> Actually the patch isn't useless. It creates a VERSION file which
> version.sh expects to exist during the building process. Without that
> file, the library reports version "[na]" instead of the correct 3.
2016-06-06 12:08 GMT+02:00 Marco Atzeri:
> builds and packages fine, but I suggest you
>
> 1) to add
>
> DIFF_EXCLUDES="VERSION"
>
> to avoid the useless creation of libsass-3.3.6-1.src.patch
Actually the patch isn't useless. It creates a VERSION file which
version.sh expects to exist during the bu
On 02/06/2016 17:09, Marcos Vives Del Sol wrote:
LibSass is an open-source, MIT-licensed implementation in C++ of a CSS
preprocessor for SASS and SCSS.
It is already packed by several mainstream distros, such as Debian
(https://packages.debian.org/source/sid/libsass) and Ubuntu
(http://packages.
LibSass is an open-source, MIT-licensed implementation in C++ of a CSS
preprocessor for SASS and SCSS.
It is already packed by several mainstream distros, such as Debian
(https://packages.debian.org/source/sid/libsass) and Ubuntu
(http://packages.ubuntu.com/xenial/libsass0)
The library is split i
12 matches
Mail list logo
