[Pkg-sass-devel] Some Bourbon with that ?

[Jonas Smedegaard]

Quoting Fredrik Unger (2014-02-26 11:45:18)
>>> Would it make sense to rather package Bourbon and Neat directly adding
>>> a thin compass layer ?
>> Not sure what you mean here.
>
> My background in ruby, sass and compass is close to zero.
> My understanding that all project are not compatible out of the box ?
> Bourbon "pure" will not run under compass?
>
> Also I was already bitten by some incompatibilities between bourbon 
> and compass, expansions that both libs does. They are after all 
> preprocessors, and do not have name-spaces..
>
> The idea would be to add the ability to run under compass in the 
> packaging, and not convert the original Bourbon code in a separate 
> github project. But maybe that is out of the scope..
>
> Eg. Source package bourbon -> final packages bourbon and 
> bourbon-compass
>
> This would not rely on https://github.com/jedfoster/bourbon-compass 
> being up to date, but also be more work, depending on what has to be 
> done to make it work. Same with Bitters that does not seem to have a 
> bitters-compass equivalent repository.
>
> Anyone can chim in with more information about the 
> relations/collaborations between the projects ?

Ahh, I now understand what you are talking about.

There is Blueprint, and there is a reimplementation in Sass/Compass.

There is Bootstrap, and there is a reimplementation in Sass/Compass.

There is Susy written directly for Sass/Compass.

There is Singularity written directly for Sass/Compass.

And there are many others, following either of those patterns...

I thought Bourbon was written directly for Sass/Compass, but you are 
right, that one also has a life of its own and a reimplemation for 
Sass/Compass.

My interest in in Sass/Compass: I want my time invested deploying a 
framework not be a total waste when (not if, none of them last forever!) 
I outgrow that one and move on the another.

If you want Bourbon, and only Bourbon, and the best quality Bourbon, 
then you should go for the original, not a reimplementation.

...and then I am sorry for my dragging you in here: I've defined to 
scope of this team to be Sass/Compass due to my interest in that (as 
described above) and it probably makes better sense that you seek 
collaborators elsewhere (perhaps the Ruby team as you suggested yourself 
to begin with?).

That said, I sure hope you want to stay, and want to help package the 
Sass/Compass implementation of Bourbon and Neat.  And suggest to the 
author of those reimplementations to do similar for Bitters :-)


>>> Is gem2deb a good start or is it better to start from scratch ?
>> I use CDBS for all my packaging, so if you choose another style you 
>> will need to find others to collaborate with than me to get your work 
>> into Debian officially.
>
> I do not mind using CDBS I just do not know it well, gem2deb was a 
> quick win.
> It generated the skeleton. I got all files set up as a first, and just 
> had to write an install file. The files themselves can then be 
> converted to CDBS.

I understand that gem2deb is fast to kickstart.  My concern is long-term 
maintenance where I have found CDBS to serve me well.  What I do when 
kickstarting a new packaging project is fetch the source code for a 
similar project, copy over the debian subdir, and adapt by hand.

Example:

  git clone git://anonscm.debian.org/git/collab-maint/compass-breakpoint-plugin

A package maintainer must know every hint declared as part of the 
packaging.  But don't let that scare you: When in a team, you are not 
the package maintainer - we are.  I'll guide you with whatever you ask 
about, and if you are not interested in learning, just want it done, 
tell me and I'll tidy up the remaining issues without explaining 
verbosely to you, and release it as a work done by our team.  Initial 
release will contain no details on who in the team did what, but for
subsequent releases the changelog documents who did what.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 966 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-sass-devel/attachments/20140226/d0cef75a/attachment.sig>