Hi there, As recently pointed out by Fredrik [1] the demand for 64-bit OSes is only getting bigger, and as more and more of us have access to 64-bit hardware it would be nice to work towards an official crux 64-bit port.
To prepare for this, we've discussed about the possible ways to manage ports, and came up with the following suggestion: - we'll keep separate core-x86_64.git and opt-x86_64.git - we'll add post commit hooks to all repositories, allowing to track changes to a port easily - ports will appear in opt-x86_64.git because they have a maintainer on this platform, not because they're in opt.git In other words, there won't be an automatic way to merge changes, however in most situations updates should be straight forward anyway, and for the rest I'd suggest to write a script which fetches the primary port, and runs some merge tool. I also suggest that we use the term "primary maintainer" (tracks upstream & makes the call whether a release should be used in CRUX, equivalent to the current maintainer) and "arch maintainer" (tracks the primary port). Being an arch maintainer should be a lot less work, and might in the future also be a good way to get into CRUX. In order to get things going, it would be nice to hear how many of you would be willing to help on this project. We can probably start with one of the existing 64-bit versions, so the initial release should be ready fairly quickly. More interesting would be to get a feeling what the costs of maintaining ports on two platforms are. Looking forward to hearing from you. Thanks, Johannes [1] http://crux.nu/bugs/index.php?do=details&task_id=280 -- Johannes Winkelmann mailto:[EMAIL PROTECTED] Zurich, Switzerland http://jw.smts.ch _______________________________________________ crux-devel mailing list [email protected] http://lists.crux.nu/mailman/listinfo/crux-devel
