hi, because my own machine has a slow network, i am building packages on a remote machine. but since they are gui packages i can't test them there, which means i'd need to commit them to the repo before installing on my local machine.
in order to update a package this means: i need to promote the package from fl:2-devel to my personal repo: update, commit, test, repeat, etc until ready, then promote source back to fl:2-devel. or i could checkout, update, build in fl:2-devel and then promote that build from rmake into my personal repo, test it, repeat until ready and hen commit to fl:2-devel. this would keep me from promoting back and forth. does anyone else have a problem like this? how do you handle testing when you build on rmake.foresightlinux.org? (can we find a better nickname for rmake.foresightlinux.org? fdev is unique and obvious, rmake in this context not so much. rmaker? rdev? rmake.flo? rflo?) greetings, martin. -- eKita - the online platform for your entire academic life hackerspace beijing - http://qike.info -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net foresight developer realss.com foresightlinux.org unix sysadmin trainer developer societyserver.org Martin Bähr working in china http://societyserver.org/mbaehr/ _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
