On 9/21/07, Christer Solskogen <[EMAIL PROTECTED]> wrote: > Aaron Griffin wrote: > > > One of the things we'd LOVE to do with PKGBUILDs is create the ability > > to build multiple packages from one PKGBUILD. That is, we could run > > make once, and create: foo, foo-libs, and foo-scripts all at the same > > time. > > In case some of you takes this email wrong; I dont want to step on > anyones toes, but I really *really* wonder why we want to split packages? > Is it not up to the developers of a program(or library, or whatnot) to > do the splitting, and not the distribution? I was under the impression > that Arch wanted to be as simple as possible. And to be simple we must > do as the developer of appplication or library(or whatnot) do. (that it, > some patches may be needed in order to forfill our own needs)
We can argue this to the cows come home. Suffice to say that it makes sense in some situations. Here's a good one, and one you may not know: The gcc-gcj and gcc-objc packages are split packages. If we were to do this the way you suggest, we should include these compilers (and any other from gcc, the GNU Compiler _Collection_) in one package. Not only is this very larger, BUT, gcc-gcj depends on gtk. If you can bandy the "KISS" term around when explaining that "pacman -S gcc" should pull in gtk (and in turn, X libs, etc etc), I will be happy to say that package splitting is no longer "KISS". _______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
