Three things.
1 - Hopefule review will have to wait until tomorrow. Why is #3
2 - My rats ... My two girls have their first litter of pups. They are being bred to feed my Burmese Python and to trade back to the pet store for mice and stuff.
I kept them together - but next time, they raise their litters separately. Shirley is being such a bitch. They both had good size litters, but Shirley is hogging all the babies - and she just doesn't have the milk to support that many. Laverne usually has a few, but Shirley will steal them. So next time they breed, they get separated before giving birth - I've had to cull the crop of the scrawny pups and feed them to my corn snakes, but I would much rather raise more healthy pups up to adult size and use them as burm food or trade. So if I separate them for their next litter, I can make sure they have about the same number of pups.
3 - I'm such a fucking a geek. I'm going through the CLFS project (Cross Compiled Linux From Scratch) - and I'm doing both 32-bit and 64-bit builds, and RPM bootstrapping them.
Talk about dependency hell - one of the applications I need for RPM bootstrapping is yum. I need yum because mock needs yum, and mock is the chroot build environment I'll use to test the final integrity of my packages and do a final bootstrap build before making an install DVD.
Anywho, yum is written in python, but yum requires a intl-tool to build. Intl-tool requires a perl module, and from there, more than a dozen other perl modules were needed to ultimately satisfy the requirements.
Yup - to properly compile and install an application written in python I need a shitload of perl modules. As much as I love Linux, that kind of dependency hell is just plain STUPID. In fairness, not all those perl modules are completely necessary - but they are for full functionality of the modules that rely on them.
It's still stupid though.
Anyway - building them did reveal a problem in my compilation of the base perl package, took me several hours of tweaking to figure out what was up and fix it - so I guess in some respects going through the dependency hell helped expose a problem in my tool chain (I would have found it anyway - just later) but it's still nuts.
Back to CLFS - I am mostly sticking to the CLFS/BCLFS way of doing things, they stick pretty much to pristine upstream source as much as possible, if you ever look at how distributions like RHEL or Fedora do things - they have some things patched up the wazoo. I'm sure the patches often have benefits, but it can get a little crazy.
I am doing a few things differently, IE I'm using chkconfig to manage the init scripts, I made some modifications to the perl build, I'll probably make some modifications to the python build - and I'm planning to use the /etc/net project for network configuration management.
If you are reading this far - you are probably a geek like me. So please, say hi
I've got hungry snakes to feed, and I know I've gone on too long, so adis until maana when I post my hopeful review.
1 - Hopefule review will have to wait until tomorrow. Why is #3
2 - My rats ... My two girls have their first litter of pups. They are being bred to feed my Burmese Python and to trade back to the pet store for mice and stuff.
I kept them together - but next time, they raise their litters separately. Shirley is being such a bitch. They both had good size litters, but Shirley is hogging all the babies - and she just doesn't have the milk to support that many. Laverne usually has a few, but Shirley will steal them. So next time they breed, they get separated before giving birth - I've had to cull the crop of the scrawny pups and feed them to my corn snakes, but I would much rather raise more healthy pups up to adult size and use them as burm food or trade. So if I separate them for their next litter, I can make sure they have about the same number of pups.
3 - I'm such a fucking a geek. I'm going through the CLFS project (Cross Compiled Linux From Scratch) - and I'm doing both 32-bit and 64-bit builds, and RPM bootstrapping them.
Talk about dependency hell - one of the applications I need for RPM bootstrapping is yum. I need yum because mock needs yum, and mock is the chroot build environment I'll use to test the final integrity of my packages and do a final bootstrap build before making an install DVD.
Anywho, yum is written in python, but yum requires a intl-tool to build. Intl-tool requires a perl module, and from there, more than a dozen other perl modules were needed to ultimately satisfy the requirements.
Yup - to properly compile and install an application written in python I need a shitload of perl modules. As much as I love Linux, that kind of dependency hell is just plain STUPID. In fairness, not all those perl modules are completely necessary - but they are for full functionality of the modules that rely on them.
It's still stupid though.
Anyway - building them did reveal a problem in my compilation of the base perl package, took me several hours of tweaking to figure out what was up and fix it - so I guess in some respects going through the dependency hell helped expose a problem in my tool chain (I would have found it anyway - just later) but it's still nuts.
Back to CLFS - I am mostly sticking to the CLFS/BCLFS way of doing things, they stick pretty much to pristine upstream source as much as possible, if you ever look at how distributions like RHEL or Fedora do things - they have some things patched up the wazoo. I'm sure the patches often have benefits, but it can get a little crazy.
I am doing a few things differently, IE I'm using chkconfig to manage the init scripts, I made some modifications to the perl build, I'll probably make some modifications to the python build - and I'm planning to use the /etc/net project for network configuration management.
If you are reading this far - you are probably a geek like me. So please, say hi
I've got hungry snakes to feed, and I know I've gone on too long, so adis until maana when I post my hopeful review.
dorcas:
thnx so much for commenting on my set it really means a lot to me *licks*