WarraWarra, Thank you for the patient reply... I'm going with an attitude to be more proactive. My scripting skills are par at best, and have found by setting up my own testing rig it would help me graduate into the testing realm of development.
I did review Gentoo's sandbox developer guide and can see that a jailed sandbox environment is perfect for development testing ebuilds binarys, this definitely clarifies my confusion with affecting my host build, and to use a chroot environment containment.
Just a few more questions?
You could just automate this using crontab and chroot environment see gentoo handbook install from scratch, let it build and then exit the jailed enviroment.
Use crontab to load your build script, make a script that mkdir, copy needed files to new directory, check if internet os on or source files for task is locally available, chroot, --sync, update portage, then either check current deps or just start the build, again test new build packs deps, do other tweaking tasks, empty temp files, do some maintenance, exit to normal user environment.
I'm familiar with cron and have a few scripts loading on certain days, which I manage through webmin. From what your saying is, I can cron entire gentoo builds? I have written certain scripts before that automount my partitions and chroot on startup and sync portage. Just haven't taken them far enough to continue a full auto build, or automate installs. Any websites you know of that could help? (not that i'm afraid of google, just some suggestions) Sounds fun... Entire build --synced and built
Equo might even be able to do your tax returns provided you can tell it where the input is and how to process it, then where to place the output and how to process the files in future for reuse. This is the concept you just need to adjust it.
This has too be the most confusing for me (Like Taxes....
) Is how, and where I can tell equo to build and process binary's and place the output for future use..? Any developer guides to equo's build process? The general Entropy wiki is vague, and caters to general use, not package development. And how can I sync my entropy/ w portage ?, so I can see any portage builds in spritz or equo. Oops... ( equo database gentoosync)
I am reviewing the equo printout.... it'll takes some review.... are there any quick how to's on package builds?
Have a look at how equo / spritz / entropy works and then tweak it's own make.conf likely adding gnome to it's USE flags.
Also you can run deptest and libtest but again are you using the gnome used by equo / entropy or the one from emerge / portage as both might be 2 different versions ?
That, I have reviewed... and know that certain Sabayon binary builds do not
have the proper flags that I require, or want. And from my recent IRC chat, I was made aware of the package delay's on the binary builds from the Gentoo portage tree to the Sabayon database (Which is perfectly ok with me, that's why I have chosen this distro, for its moving forward attitude, and giving the user more control over the OS, and easy installs). That's why I want an independent repository for testing newer ebuilds, or custom ebuilds, and to pull from the latest overlays (~amd64 & ~x86) and from SVN, or Git sources to test and build new binary builds. Just a clarification, is the Sabayon development team building all binary's from directly from source without the Gentoo ebuilds?... Please excuse any of my amateur development ignorance.
2 guys and 2 bank accounts, what ?
Check both /etc/make.conf and equo / entropy make.conf and make sure they speak the same languages and uses the same parts as this will have a effect on what and how it installs
This is where I am confused between the two... Again in my latest IRC chat I was recommended to keep all CFLAGS...etc etc.. the same unless I choose to use portage over entropy. With the exception of USE flags, so they speak the same. And was later recommended in IRC to just stick with the package.use files... Which I'm happily obliged with for version control because of delays, or any conflicts in the configuration files of different versions in Gentoo portage and Entropy.
I'm getting.. it now... if I run a "equo database gentoosync" and then a "equo world" and the USE flags don't match my original emerge, then "equo world " asks for an update, or downgrade, if the version or USE flags are not the same? Is this right? And the only way to correct this is to edit the make.confs and package.use files, for both package managers. I always assumed that even if my USE flags where declared, it wouldn't matter if a binary package that is already built with its predetermined USE flags. So even with a gentoosync, Entropy would always ask for an upgrade or downgrade. Is this correct? And if so, would I need to mask them from an Entropy update if the binary's don't have the proper USE flags.?
1) I'd like to know how Sabayon team builds binary's from source, or ebuilds
2) And if the binary's built using equo, a How To, or developer guide would be great
3) I'm just an amateur trying to build a personal repo... that I can use to grow my skills, and eventually make a secondary mainstream repo for users to share. I have the bandwidth and computer power to at least try it
Thx a again for your any help.... Just wanna go to the next level... Again apologies for an extremely winded post...