Takeshi Asano wrote: > Thank you, Bart. > > Do you already have idea to enable client to get list of possible > values of facet from repository to enable selection-based > UI to user? >
Like most of these kinds of problems, I'd like to solve this w/ search rather than a special API. > I'm considering more detailed design for l10n facet, including > whether the wildcard is enough for specifying set of locales > and whether adding some map/alias in package side > would be reasonable or not. Great; if you've got some ideas please chime in... I'd like to make sure we've got the framework correct the first time around. The first part I'm implementing is variants, since those are needed to support fat packages so sparc and i386 bits can be kept in the same (existing) repos. > > BTW, using current mechanism to import Nevada SVR4 > packages to IPS, merging packages in IPS could > cause cases that multiple IPS packages have legacy > information on a SVR4 package. > Can I understand this will not cause problem? > That's correct; that's already the case w/ existing packages. SUNWcs and SUNWckr both have legacy entries for SUNWclofi, since they both get components from that package, and lots of packages have legacy entries for SUNWfixes, a temporary package used to contain modified files during the package import process. - Bart -- Bart Smaalders Solaris Kernel Performance [email protected] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
