I am trying to install a css less compiler, lessc. I have found a wiki online that explains how to do just that on a debian server. I have followed the instructions (with a few tweaks to get all the steps to work) and I get this message:
What I understand from that is that the Ultimately, I'd like to understand (1) the process of installing external packages, (2) where to put them, (3) where to find them, (4) how to remove them from your environment, all that, within the context of webfaction. This link here answers alot of those questions, but some pieces are missing. Anyone who has had experience installing css compilers (less, sass) and node could give me a hand? asked 19 Sep '12, 17:18 mjlavoie |
Overview The 'lessc' program is actually a javascript file which is run via node, so you'll first need to install node using this related community post, or manually using our home-install guide. Then, once that's done, grab Less CSS. The installation procedure for lessc is similar to the home-install guide, except that it seems that less CSS doesn't use the "./configure" step. After installing node, you should be able to just run "make" or use bin/lessc directly. Guide Install Recently node is much easier to install than in the past, so we can just install it as any other normal source-code application:
Discussion Installing software has three parts. First, you configure it, which means changing and setting the compile-time options. Many pieces of software can be compiled in different ways, with different internal paths, and with certain options like multithreading turned on or off. The Some programs are so simple that don't have any compile-time options at all, or they have just a handful which can be manually set inside of the The next step is to compile the software. This is what the The final step is to install the software. Installation usually means nothing more than copy-pasting those binaries into their new permanent locations. In the first example here where we installed node, the The There is a lot more to installation than this. For example, sometimes some software needs to compile in dependencies for other software, which is where the If you're looking for in-depth knowledge and examples about compiling and installing software on linux, the book How Linux Works by Brian Ward is the best material on the subject that I've seen, so I'd strongly recommend it as the best place to start to really understand what's going on. Hope that helps! answered 19 Sep '12, 20:32 ryans ♦♦ You sir are a gentleman! I really appreciate the (very complete) answer you took the time to write. In the set of instructions provided, "which node", instead of the expected results outputs as follows: [xxxxxxxx@xxxxxx node-v0.8.9]$ which node /usr/bin/which: no node in (/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/dell/srvadmin/bin:/home/xxxxxxxx/bin) Ok, it's not there. Well perhaps creating a soft link to out/Release/node in ~/bin/ would work since installing is sometimes a matter of copying bin and lib in the right folders, so I did: [xxxxxxxx@xxxxxx node-v0.8.9]$ ln -s out/Release/node ../../bin/node [xxxxxxxx@xxxxxx node-v0.8.9]$ ll ../../bin/ Listing the contents of bin prints out "node -> out/Release/node" all in red. Trying "which node" gives the same results as before. I am stumped.
(20 Sep '12, 20:14)
mjlavoie
It is difficult to see why it is failing from here. It is likely related to the paths, and we could investigate more with a support ticket.
(20 Sep '12, 23:45)
johns
Thank you very much for this informative write-up. This helped me a lot!
(11 Jul '13, 13:41)
vcatalano
|