-
Notifications
You must be signed in to change notification settings - Fork 5
morevnaproject/morevna-builds
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
Install: run all commands from root (as superuser) install dependency packages: you need: bash sudo uuid-runtime aufs-tools fuse genisoimage mutt for apt based OS use command: apt-get install bash sudo uuid-runtime aufs-tools fuse genisoimage mutt create and edit config file: use config.sh.blank as a base: cp config.sh.blank config.sh we use config (some_path is a fake): PACKET_BUILD_DIR=/some_path/builder-packet chrooter() { export CHROOTER_PREFIX="/some_path_to_mount" $BASE_DIR/chrooter/chrooter.sh $@ } OPENTOONZ_TESTING_TAG="morevna" export EMAIL_FAILED="[email protected]" export EMAIL_SUCCESS="$EMAIL_FAILED" export EMAIL_SUBJECT="builder task finished" for emails configure ~/.muttrc, for example: set smtp_url=smtps://login:[email protected] set from="My Mail Bot <[email protected]>" set record= see "background tasks" below download virtual environment: you may download our (we are Morevna Project team) os images from: https://coolbug.org/downloads/morevna/builder-images/ you need two files: https://coolbug.org/downloads/morevna/builder-images/morevnaproject_build-debian-7-32.iso https://coolbug.org/downloads/morevna/builder-images/morevnaproject_build-debian-7-64.iso approximate 6.5Gb, place both into chrooter/images/ build virtual environment: if you does not want to download os images you can build it before begin you may configure debian mirror in files: env/debian-7-32bit/files/sources.list env/debian-7-64bit/files/sources.list env/debian-7-32bit/build-iso.sh into variable apt_mirror env/debian-7-64bit/build-iso.sh into variable apt_mirror here you still can download a base debian images from: https://coolbug.org/downloads/morevna/builder-images/debian-wheezy-i386.iso https://coolbug.org/downloads/morevna/builder-images/debian-wheezy-amd64.iso approximate 500Mb, place first into env/debian-7-32bit and second into env/debian-7-64bit or build these images from scratch by debootstrap install debootstarp: apt-get install debootstrap and build base debian images cd env/debian-7-32bit # go to env/debian-7-32bit ./build-iso.sh cd ../debian-7-64bit # go to env/debian-7-64bit ./build-iso.sh cd ../.. # go back after that will appear two new files: env/debian-7-32bit/debian-wheezy-i386.iso env/debian-7-64bit/debian-wheezy-amd64.iso now when you have files debian-wheezy-XXXX.iso you can build os images for builder it's a long process because it will build GCC and MinGW from scratch run commands: cd env/debian-7-32bit # go to env/debian-7-32bit ./build-base.sh # just to copy base os image into chrooter/images ./build.sh # a long build process cd ../debian-7-64bit # go to env/debian-7-64bit ./build-base.sh # just to copy base os image into chrooter/images ./build.sh # a long build process cd ../.. # go back build environment ready installation done also you may download full backets build data made by us: https://coolbug.org/downloads/morevna/builder-images/ https://coolbug.org/downloads/morevna/builder-images/builder-packets--YYYY-MM-DD.tar.gz approximate 20Gb compressed and 75Gb after decompress NB: build data contains a lot of hardlinks so make sure that you unpack it properly (tar -xf) Let's build something: now you may build packages by macro script: see files ./build-*.sh also you can add hooks to publish built packages: for example create file publish/publish-synfigstudio.sh with content: #!/bin/bash cp "$1" /var/www/public/downloads/ when build is done new synfigstudio packge will placed into web-site directory you may look file publish/publish.sh for more info run internal builder commands in virtual environment: cd env ./run.sh some_command also you may use: env/debian-7-32bit/run.sh env/debian-7-64bit/run.sh env/debian-7-64bit/win32.sh env/debian-7-64bit/win64.sh run build commands in native environment ./run-native.sh some_command build a selected package: cd env ./run.sh env_release MEGAPROGRAM-1.0.0 take files from directory env-builder-data/build/packet/linux-x64/MEGAPROGRAM-1.0.0/env_release or your_build_path/packet/linux-x64/MEGAPROGRAM-1.0.0/env_release "dry_run" option for paranoics: ./run.sh dry_run with_deps unpack MEGAPROGRAM-1.0.0 List of commands <action> <packet> do <action> for <packet> List of actions: - download - unpack - build - install - install_release - envdeps - envdeps_release - env - env_release dry_run <any other command> - simulate activity with_deps <command> <packet> - execute <command> for <packet> and all deps for example, you can call download for all deps without build: run.sh with_deps download mypacket clean_ACTION <packet> - remove all data of completed ACTION for <packet> ex.: clean_unpack MEGAPROGRAM-1.0.0 clean_all_unpack <packet> - cleans download and unpack see: clean_ACTION <packet> clean_all_env <packet> - cleans install, install_release, envdeps, envdeps_release, env and env_release see: clean_ACTION <packet> clean_all_install <packet> - cleans all env and build see: clean_all_env <packet>, clean_ACTION <packet> clean_all <packet> - remove all data of all completed actions for <packet> set_undone_ACTION <packet> set_undone_all_unpack <packet> set_undone_all_env <packet> set_undone_all_install <packet> set_undone_all <packet> - mark ACTION incomplete for <packet>, but keep action data see: clean_* comands shell <packet> - run shell in environment of <packet> chain <command> chain <other_command> ... - run several command sequentially wihtout remounting of environment to increase speed see also env-builder-data/build/script/common/manager.sh Background tasks: to call task in background use: backgrouns.sh some_command command will run in background and result will be sent to email (see config.sh) if you do not want to receive emai about success result (look only errors), call: backgrouns.sh -q some_command logs stored in log/background.log Troubles: sometimes virtual environmens does not unmounted properly to clear this you need to unmount all mounts for */chrooter-* look mounts list by command: mount unmount by command: umount "/some_path/chrooter-SOME_UUID" or with "force" option umount -f "/some_path/chrooter-SOME_UUID" or with "lazy" option umount -l "/some_path/chrooter-SOME_UUID" and check againt with mount after that remove the files you MUST do unmount before, if some dir are still mounted you can remove some system files we recommend to check content of directories before remove option "--one-file-system" for additional protection but anyway BE CAREFULL!! command: rm -rf --one-file-system /some_path/chrooter-*
About
No description, website, or topics provided.
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published