Hi all, Developers/packagers may want to take note of the attached post to the pkg-discuss list. As we move forward with this project, it'll probably make sense to deliver "clusters" or "incorporations" of various bundles of components into Indiana.
Toward that end, it's worth thinking about what kind of functionality we need to "pkg install ruby_rails_lighttpd" or "pkg install amp" or even "pkg install webstack". The other big question in my mind here is how we'd handle post-install configuration (if at all). I know Jyri has followed this and thought about it some. Are there any specific things we'll need to be able to roll forward say the MySQL package, or handle a shared dpendency like curl? There's nothing I can think of at the moment, but now is the time to think it through and ask about it if we can. - Matt -- Matt Ingenthron - Web Infrastructure Solutions Architect Sun Microsystems, Inc. - Global Systems Practice http://blogs.sun.com/mingenthron/ email: matt.ingenthron at sun.com Phone: 310-242-6439 -------------- next part -------------- An embedded message was scrubbed... From: Stephen Hahn <s...@sun.com> Subject: [pkg-discuss] Package namespace Date: Mon, 31 Mar 2008 14:12:45 -0700 Size: 12601 URL: <http://mail.opensolaris.org/pipermail/webstack-discuss/attachments/20080331/db3c7806/attachment.nws>
