Heyo Jue, First of all, I'm very glad of having your response. Thanks a lot. Juergen Daubert wrote:
On Wed, May 21, 2008 at 09:41:31PM +0200, Jose V Beneyto wrote:
Hi people,
Hi Jose,
Apparently, ATM don't exist a unified way for testing/developing ports. As we known, developers are using prtutils, chroot environments or unfortunately other are using their own crux system for building and testing their ports, and that sounds terrible in some cases.
For that, we are working on 'safe-env', a environment similar to a "freshinstall", where testing ports and try to discover bugs, and also the most issues that crux users can find when they are building ports for their systems.
it would help much if you could clarify the following points:
- which problems do you try to fix with safe-env
Encourage lacy people to use a chroot environment, by saving a lot of his time. The main goal, as I exposed in my other mails and pitillo too, was keeping the idea of ChrootTesting, but being more automated for getting it running in a easy way, without spend time for build the environment.
- how does it work, e.g. some kind of description or pseudo-code
1 - first of all select what kind of environment you want to have (crux_version, source_iso, img_size, img_fstype, etc) $ vim etc/safe-env.conf 2 - start the automation and create one environment with the options you selected previously - init does: * download selected iso * check md5 * mount iso with loop * create (with dd) a new fs image (with fstype/size you selected) * mount the fsimage * fakesetup all core ports from iso loop-mounted image to fsimage (fakesetup iso/mnt mnt/) * finish the fsimage (it will be named 'core' by default, and stored in img/core) * optional that can be added: execute you own extra post-installations tasks * umount all $ sudo ./safe-env init 3 - use the environment * mount img/core * execute fakelogin and whatever you personalize on init $ sudo ./safe-env use core 4 - test the building process of a port using prt-get depinst and snapshots (for more info doc/HOWTO-Working-with-prt-clean.txt) * make the inital snapshot # prt-clean store "Initial snaphot" * install depinstallation of a port # prt-get depinst foo * if it success # prt-clean clean (or prt-clean restore 1) * if not report the problem for building the port or his dependencies [...] * exit from the safe-env # exit Also can be used in many different ways, just test it.
thanks and regards Juergen Thanks you too and best regards
Jose V Beneyto