As I
think open software is the way, I don't see any objective in making it closed source. Think of it a little bit: every OSDever on here has its own project. Almost no one here takes care of the other ones' projects.
BUT, we certainly, even not noticing it, participate other projects when answering/posting threads. Please don't misunderstand me. I'm only presenting my personal opinion. If you wanna make it privative and/or lucrative software, it's your software
.
Touching the other topic; I don't know how sortie makes those stuffed wiki articles from nowhere; but that's for another thread
. Think more in depth about it: what if
/usr/bin/gcc isn't a symlink? That's merely possible (in a fucked up system). What if BTW it's
NOT the GNU Compiler Collection, but rather something a crazy servermaster put in there? Also, if you're working in Ubuntu it's even worse.
APT and friends use
/usr/xxx for package-managed stuff. If you still wanna install something system-wide, do it in
/usr/local/xxx at least! Or even better, modify your script to use the system's utilities.
Let's do an experiment:
1- Compile and install GCC (GNU C Compiler...) with these flags:
Code:
--prefix=/usr --program-prefix=""
2- Let's run your buildscript...
3- Congratulations! You just trashed GCC with and older version! Also, you now have LOTS of bloated /usr folders due to the old GCC's libraries and runtime support. Also, you took 30 minutes to build GCC (x2 with that of your buildscript) and went nowhere!
What happens? The servermaster will come and see what you just did with his lovely GCC. The webmaster will then execute this on his terminal:
Code:
sudo userdel -r you
_________________
Happy New Code!
Hello World in Brainfuck :
Code:
++++++++[>++++[>++>+++>+++>+<<<<-]>+>+>->>+[<]<-]>>.>---.+++++++..+++.>>.<-.<.+++.------.--------.>>+.>++.