>> In the sprit of the coreutils case, I'd like to suggest >> SUNWgnu-readline. > > On the other hand "coreutils" might be more generic than "readline" and > thus require the "gnu" prefix. Are all the /usr/gnu cases going to be > SUNWgnu-XXX?
That's a good question but I though one of the values of naming it such was to more easily identify that this is one of the GNU-based packages. Otherwise, I don't have any strong preference. >>> /usr/gnu/lib/libhistory.a Uncommitted Static library >>> /usr/gnu/lib/libreadline.a Uncommitted Static library >>> **FIXME** presume shouldn't deliver these, even though SFWrline did? >> >> Agreed - we shouldn't be shipping the static variants. > > Is there utility to doing so because it's a GPL library? The ARCs have > historically encouraged project teams insistent on using readline to link > it into their objects statically, and this would make such a thing easier. > I'm not sure if it makes as much sense under the present circumstances, > though. I could see that if we were delivering this as /usr/lib/libhistory.a and /usr/lib/libreadline.a. But since we're putting it in /usr/gnu for now until a general decision is made on such libraries in /usr/lib, it seems delivering just the dynamic version is fine. dsc
