caminoix,
>>
staying away from command line is certainly helpful. it's not that i'm very much against it, but it might really be discouraging for a complete newbie just like me
>>
In Aus, the tourist industry have a jingle for holidaying in the top end. What we call the 'never never' ...
"You'll never never know, if you never nerver go" (grin) (i couldn't resist that one)
Command lines and source compiles. Keep it simple, experiment with very small programs, in order to get an initial feel.
>>
just one question more: what do i do if installing from source fails 'cause i don't know where to find files it says it needs or it doesn't say what files it needs,
>>
Learn by doing ...
Post the erro here ...
pipe the output to a log ... ie;
]$ make 2>&1 | tee logfile
Then just start with the first error first. Sometimes, pasting a whole error output string on a google search will return info on that particular error. Lots of errors can be missleading, as often those that follow are just leading on from the previous. That is, if you can solve the initial ones, often the layer will disapear. And like all things, it's just something that needs to be done in practice.
Some Common Error Trivia:
-----------------------------------------
"carn't find symbole"
often it is trying to link with an incompatible library version. it probably wonts a later version.
"compiler can't create executables"
look for a typo in the configure script, look into the config.log file, backing through it to anything to do with the linking stage of a test compile. There is likely a missing space between two cli switches concerned with the linking.
"carn't find libblah"
your probably trying to compile Qt (couldn't resist that one either )
>>
and finally dpkg -i only gets me an installed and uncompressed but uncompiled source?
>>
The switch is for "installing" a binary package. Not unpacking source. Look into your manuals, including "dpkg-deb".
The "--dry-run" switch can be handy for doing dummy runs, just to extract info.
dpkgmay not have a direct "what-depends" switch, as does the "rpm" system, but ...
"--dry-run -r <packagename>" and
"--dry-run -P <packagename>"
will safely tell you what is dependent on that package.
jm
HyperX FURY DDR4 16GB 32GB 64GB 2666MHz PC4-21300 Desktop RAM Memory DIMM 288Pin
$119.80
A-Tech 8GB DDR3 1600 PC3-12800 Laptop SODIMM 204-Pin Memory RAM PC3L DDR3L 1x 8G
$13.99
Team T-FORCE VULCAN Z 16GB (2 x 8GB) 288-Pin PC RAM DDR4 3200 (PC4 25600) XMP
$35.99
HyperX FURY DDR3 8GB 16GB 32GB 1600 MHz PC3-12800 Desktop RAM Memory DIMM 240pin
$12.90
8GB PC3L-12800S 1600MHz SODIMM DDR3 RAM | Grade A
$12.00
Crucial DDR3L 16GB 1600 2x 8GB PC3-12800 Laptop SODIMM Memory RAM PC3 16G DDR3
$21.50
Crucial 16GB (2x 8GB) Kit DDR3L 1600MHz PC3-12800 UDIMM Desktop 240-Pin CL11 RAM
$23.33
CORSAIR Vengeance RGB Pro 32GB (2 x 16GB) 288-Pin PC RAM DDR4 3600 (PC4 28800)
$79.95
A-Tech 64GB Kit 2x 32GB PC4-25600 Laptop SODIMM DDR4 3200 MHz 260-Pin Memory RAM
$123.99
HyperX FURY DDR4 16GB 3200 MHz PC4-25600 Desktop RAM Memory DIMM 288pin 2x 16GB
$127.20