>> mutt/Makefile.sfw: >> >> o line 128: I'm not terribly happy with this, but I don't know >> whether our gettext supports locale aliasing. Anyone know? >> Should we file an RFE if it doesn't? >> >> o line 129: This should probably be /etc/mutt. > > I wavered a bit on this, but ultimately chose /usr/share/mutt/etc in > part to avoid conflicts with the system's /etc/mime.types. But I can > be persuaded here.
>> slang/Makefile.sfw: >> >> o line 82: likely sysconfdir should be under /etc here, too. > > Given that slsh is not going to be widely used, I don't feel it merits > cluttering up /etc with slsh.rc. As with mutt, I can be persuaded. Are these files installed under /usr/share/mutt editable by the user? If so, they shouldn't be delivered under /usr which may be read-only. >> SUNWmutt/protoype_com: >> >> o line 120ff: Is there a reason that message files are going in >> /usr/share, rather than /usr/lib? > > mutt elects to put them there, and there appears to be precedent: > SUNWpostgr-libs and SUNWgnome-dtlogin-integration, among others, also > prefer /usr/share. I think Norm Jacobs can provide some guidance here because I never can remember the correct convention. >> All of these components are at least partly GPLv2. Typically legal >> requires that we put a disclaimer at the top of the copyright file >> (or something similar, but that's how we've been interpreting that >> requirement) that says that we're distributing under v2 *only*, and >> no later versions. Were you not asked to do something like this? > > Thanks for the pointer -- I did not notice this requirement in the TOI > pdf. I'll add the preambles to each. Incidentally, I notice there > are several GPL-licenced packages in SFW that don't carry this > preamble. I'll take a look but I thought this was documented in the presentation. But you're correct, there are many components currently in SFW which need to be updated (this is a fairly new requirement.) dsc
