<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
Hi Samuel,<br>
<br>
I'd say Solution 1 is the simplest. As it only adds one new
dependency.<br>
<br>
For Solution 2, seems we will depend on more packages. Are there
packages for NVM, NodeJs and NPM in all supported distros (Fedora,
RHEL, openSUSE, Ubuntu) ?<br>
If you think Solution 2 will give us more benefits in future, I
support you on that.<br>
<br>
Just for register, I don't like Solution 3. =)<br>
<br>
Regards,<br>
Aline Manera<br>
<br>
<div class="moz-cite-prefix">On 05/10/2015 16:13, Samuel Henrique De
Oliveira Guimaraes wrote:<br>
</div>
<blockquote
cite="mid:7eb8e4523e144f3ea139e3211d4f7c24@serv031.corp.eldorado.org.br"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        mso-fareast-language:EN-US;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi team,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">I’ve tried to add
libsass in the project conf files since we need this library
to build the new-ui in Wok. Turns out there isn’t any
libsass package in Fedora & OpenSUSE repositories. I
came with three possible solutions to install this ui
build-only dependency:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Soloution 1:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">-Install PyPi manager
(Python Package Index)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">-Install libsass using
pypi during Kimchi/Wok setup (pip install libsass);<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Solution 2:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">-Install NVM;<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">-Install NodeJS and NPM;<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">-Install NodeJS libsass
port during Kimchi/Wok setup (npm install -g libsass);<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Solution 3:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">-Change .gitignore to
include the CSS files that were supposed to be generated by
Libsass and if the dev/contributor want to edit the CSS
files, instruct him/her to manually install libsass.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">BTW, with solution 2 we
could also benefit from Bower (a front-end package manager
that I already mentioned few e-mails ago in the ML) that
could install Bootstrap Sass and Bootstrap-Select Sass
sources in the dev/contributor machine. i.e. no need for
“src/vendor” folder, it also ensures that the devs are using
the correct version of any of these libraries and we could
extend its use to other things like JS libs (jQuery-UI,
jQuery, Bootstrap JS) and UI tests (ESLint, Browsersync.io).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">In the meantime I’m
sticking with solution 3 until the new-ui CSS is not
complete.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Samuel<o:p></o:p></span></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>