> DD> so yeah, it's probably what people want. The only exception would be, > DD> for example, if you were packaging for a distro and you want to > DD> support upgrading. In those cases, it's better for the packaging if > DD> the package version numbers match the upstream version numbers, which > DD> means separate packages. > So, there is contradiction between requirements :)
Not quite. For distros, you have a separate package which is the "collector" for all the other packages. For example, if you installed "mspgcc" then that package would automatically pull in all the sub-packages like gcc, binutils, etc, and let the sub-packages update independently of the collector package. > And it contradicts to building separate packages too, because you > could not build and install half of a package Not much I can help with here, the upstream sources are what they are. Even porting linux to new architectures, we run into these problems. The solution is that someone does it manually once, and after that, you build each package using the previous version of the other package each time. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
