Hi people,
As surely someone has known, pitillo and me are involved on developing a
safe environment where test crux ports.
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.
We are trying to keep the environment as simple as possible (KISS),
giving freedom to respect people's customs or preferences working daily
with CRUX, but having the security of a minimal and secure environment.
Surely we have errors or other things that can be done better, without
doubt, but now our first objective is to know if CRUX people can see it
like as a idea that can be done better in a future, and if it can be of
benefit for all the community.
The environment consist in 2 scripts: safe-env and prt-clean:
- with safe-env we can build a "freshinstall" environment and play with it.
- also, with prt-clean we can take snapshots at different moments of our
environment and then delete ports between snapshots (taking first a
freshinstall snapshot)
Being minimal it can be flex and we can give it more uses, personally
I'm using it to build uCRUX packages for my old 486 laptop, so I don't
spend hours and hours compiling on it.
Finally, we will glad to known your opinions/suggestions/etc about that.
last release:
http://mikeux.dyndns.org/crux/distfiles/safe-env-0.1-svn162.tar.bz2
svn repository: svn://mikeux.dyndns.org/safe-env/trunk
Thanks in advance, and best regards,
Jose V Beneyto
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has been changed. The changes are listed below. For full information about what has changed, visit the URL and click the History tab.
FS#283 - pkgmk, build from existing work dir
User who did this: Bartlomiej Palmowski (mxq)
Task details edited:
-------
pkgmk build from existing work dir (would work well in conjunction with extract only #271), handy to check with the sources quickly modify by hand ,then build from modified sources, and then modify Pkgfile. It also gives a warning after succesful build and removes TARGET, just to be sure Pkgfile will be modified and checked.
-------
More information can be found at the following URL:
http://crux.nu/bugs/index.php?do=details&task_id=283
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
You have been assigned the following task:
FS#283 - pkgmk, build from existing work dir
User who did this - Bartlomiej Palmowski (mxq)
More information can be found at the following URL:
http://crux.nu/bugs/index.php?do=details&task_id=283
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Bartlomiej Palmowski (mxq)
Attached to Project - CRUX
Summary - pkgmk, build from existing work dir
Task Type - Feature Request
Category - pkgutils
Status - New
Assigned To - CRUX Developers
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - pkgmk build from existing work dir (would work well in conjunction with extract only #271), handy to check with the sources quickly modify then build, and then modify Pkgfile. It also gives a warning after succesful build and removes TARGET, just to be sure Pkgfile will be modified and checked.
More information can be found at the following URL:
http://crux.nu/bugs/index.php?do=details&task_id=283
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hi
(this is my first post here \:D/)
Pkgmk deletes work dir before performing build, I think it would be
very handy feature to optionally allow building package from existing
work dir, it would work very well altogether with nipuL's
pkgutils-5.32.0-extract-only.patch[1], instead of pkgmk -do, then
extracting sources manually, then modifiing Pkgfile, making patches, and
then checking if it works, it would be easier to do firstly pkgmk -do -e
to download and extract sources, "mess" with them, and then pkgmk -b to
build from already modified sources.
It would speed up port creating and debugging process, and would be
useful not only for port maintainers but also end users trying to tweak
or simply make ports to work. You may think of it as similar to putting
read KEY inside build(). Such feature is included in other distros'
package builders i.e. "makepkg -e" etc. etc.
Patch attached.
Best regards
Bartlomiej Palmowski
1 - http://article.gmane.org/gmane.linux.distributions.crux.general/2940
diff -pruN pkgutils-5.32.0.orig/pkgmk.in pkgutils-5.32.0/pkgmk.in
--- pkgutils-5.32.0.orig/pkgmk.in 2008-03-01 10:18:03.000000000 +0100
+++ pkgutils-5.32.0/pkgmk.in 2008-05-22 21:59:50.000000000 +0200
@@ -339,8 +339,11 @@ build_package() {
umask 022
cd $PKGMK_ROOT
+
+ if [[ $PKGMK_BUILD = "no" ]] ; then
rm -rf $PKGMK_WORK_DIR
mkdir -p $SRC $PKG
+ fi
if [ "$PKGMK_IGNORE_MD5SUM" = "no" ]; then
check_md5sum
@@ -352,7 +355,7 @@ build_package() {
info "Building '$TARGET'."
- unpack_source
+ [[ $PKGMK_BUILD = "yes" ]] || unpack_source
cd $SRC
(set -e -x ; build)
@@ -508,6 +511,7 @@ print_help() {
echo " -f, --force build package even if it appears to be up to date"
echo " -c, --clean remove package and downloaded files"
echo " -kw, --keep-work keep temporary working directory"
+ echo " -b --build build from existing work directory"
echo " -cf, --config-file <file> use alternative configuration file"
echo " -v, --version print version and exit "
echo " -h, --help print help and exit"
@@ -547,6 +551,8 @@ parse_options() {
PKGMK_CLEAN="yes" ;;
-kw|--keep-work)
PKGMK_KEEP_WORK="yes" ;;
+ -b|--build)
+ PKGMK_BUILD="yes" ;;
-cf|--config-file)
if [ ! "$2" ]; then
echo "`basename $PKGMK_COMMAND`: option $1 requires an argument"
@@ -667,6 +673,7 @@ PKGMK_UPDATE_FOOTPRINT="no"
PKGMK_IGNORE_FOOTPRINT="no"
PKGMK_FORCE="no"
PKGMK_KEEP_WORK="no"
+PKGMK_BUILD="no"
PKGMK_UPDATE_MD5SUM="no"
PKGMK_IGNORE_MD5SUM="no"
PKGMK_CHECK_MD5SUM="no"
