Hi, On Wed, 2010-01-06 at 09:26 -0800, Stephen Hahn wrote: > Now that the bulk of the feature development for pkg(5) is finished > for 2010.next, I'd like to get a few of the distribution-oriented > changes lined up as well. First among these is Rich's proposed set of > package renames, as proposed in > > http://defect.opensolaris.org/bz/show_bug.cgi?id=6186
Some comments about the proposed GNOME package naming. It's not clear what qualifies as "gnome2" For example, I'd say bluefish does not. It has a gtk-based front-end but that's it. Apart from that, it would gladly run on KDE, Xfce or anything else. In fact, Xfce has very few "commands" (I'll get back to this later) of its own, it runs GNOME applications. Similarly, Qt-based apps can be run on GNOME (e.g. VirtualBox) just fine. Some projects can be built with different toolkits. So I would suggest separating desktop environments and desktop applications. gnome2/... xfce4/... kde4/... web/firefox2 web/editor/bluefish image/editor/gimp image/viewer/gthumb Some applications are closely tied to a desktop environment, (e.g. file managers) and these should be under the appropriate desktop environment's hierarchy. What's under these categories is the next issue. "command" doesn't make any sense to me. Many projects have "commands", libraries, Python modules, documentation, localisation, etc... If we don't intend to split them up along these lines, we shouldn't throw them all under something like "command". I agree with those who suggested that the basenames should match the project names, e.g. gnome2/file-manager/nautilus, gnome2/accessibility/screen-reader/orca. I also find the proposed GNOME library renames confusing: some libraries under system/library/gnome2 others under library/gnome2 and then again, several GNOME libraries come with the applications, so I assume those would not be split out. Python modules, however, should be split so they can be built and packaged for several different Python versions and I think all Python modules should live under Python categories, something like: system/python/python24 system/python/python26 python24/pygtk python26/pygtk python24/mysql-python python26/mysql-python Localisation and documentation should be facets of the packages, not separate packages. I know we are not there yet with the installer, but perhaps we should just leave those packages alone then rather than introducing new package names that will go away soon. I guess I should stop here and wait for responses before going into the details of specific packages. Laca _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
