Tom Mueller (pkg-discuss) wrote: > Shawn Walker wrote: >> Tom Mueller (pkg-discuss) wrote: >>> The package display menu assumes that packages are put into the >>> repository with a common release/branch value indicating a set of >>> packages that go together. While this happens to be true for >>> OpenSolaris now, it will not generally be true for other >>> repositories. For example, take a look at the Glassfish V3 Prelude >>> repository: http://pkg.sun.com/glassfish/v3prelude/release/ >> >> Actually, it doesn't assume that. If you'll look at the code in >> index.shtml or catalog.shtml, you'll note that it calls >> shared.get_releases() to get the release information, and if it can't, >> it falls back to just listing every package. >> >> I definitely had the glassfish repository in mind when I wrote this. > Cool. I missed that feature of this when I first looked at it. > > Could the OpenSolaris-specific implementation of shared.shtml be made > part of the OpenSolaris theme? And an alternate default implementation
It could, however, I'd rather not do that for now as: 1) It won't harm anything, since I already have a fallback case as I pointed out earlier. 2) My primary focus is on OpenSolaris repositories with this release. > provided that doesn't have the dependencies on the entire package and > the use of branch numbers? If you're asking for an alternate implementation that somehow gets version information to browse by, I don't see how else I could get that at the moment. However, I've documented this in bug 5341, and will revisit this then. As I mentioned before, there is already a fallback case if it can't get the version information because entire doesn't exist, etc. Thanks for your feedback, -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
