Ethan Erchinger wrote: >> Then perhaps the source for the package and build script should be > made >> available in a source repository. This should be possible for at least > the >> F/OSS based packages. >> >> Right now there is a hole in the pam_krb5-module, that needs to be > fixed. >> It would be nice to have a way to rebuild any package with te same >> configuration as the one installed. >> >> /Klas > > I completely agree with this statement. The inability to rebuild any > package from source, in the exact same way, is a pretty big hole in the > pkg system. This type of problem has been solved many, many times, so > there are plenty of examples of how this could/should be done.
Even if pkg(5) did have a build facility integrated, it wouldn't matter as the majority of binaries produced by Sun don't share a common build system. ON is built with nightly, JDS is built with CBE, and so on. In addition, package boundaries are not defined by source code boundaries. In other words, a developer may take binaries from multiple source code drops to build a single package. The lack of a build system is not "a hole"; it was intentional (for now). The design of pkg(5) asserts that a packaging system is "a way to collect and organize the set of components, binary and otherwise, into an always "bootable" flow of change" [1]. -- Shawn Walker [1] http://blogs.sun.com/sch/entry/pkg_leaving_the_build_system
