Am 30.01.2014 14:46, schrieb Niels Grewe: > If there are issues with it, please help us identify them.
The most troublesome parts are the requirement for GNUstep.sh, the existence of GNUSTEP_MAKEFILES and GNUSTEP_INSTALLATION_DOMAIN and the apparent lack of a concept to deal with bundle files distributed by FHS standards (like picture resources of a framework going entirely elsewhere than the binaries). That's what I could identify so far. Solving this isn't impossible, we have gnustep-config and openapp. If you're willing to help, there's a GNUstep Developers team on Launchpad which focusses on just getting the stuff working on Debian/Ubuntu. Looking at the amount of changes required I guess it needs an own code repo as well. > PS: Just to be sure: You are not referring to the problems installing > the -make documentation, right? This was just one of many. The very same problem happens in -base and -gui, but I didn't bring it up in fear of things getting worse. For even more see above. The principle of packaging is very simple: one source package creates several binary packages (like -common, lib-, lib-...-dev, -doc). Then craft a makefile (named "rules") which implements three targets: build, binary and clean. "Build" configures and compiles, "binary" installs this into a tmp directory and copies files into per-binary-package directories with debian helper scripts. A debian package is just one of these per-binary directories tarred up. The packaging process goes like this: cd debian make -f rules clean make -f rules build make -f rules binary tar ... There are more obstacles, like dependencies, but these aren't code or build system related. Also, this description is a bit simplified. Markus -- - - - - - - - - - - - - - - - - - - - Dipl. Ing. (FH) Markus Hitter http://www.reprap-diy.com/ http://www.jump-ing.de/ _______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
