Danek Duvall wrote: > On Tue, Feb 19, 2008 at 06:28:23PM -0800, Gary Winiger wrote: > > >>>> Why? >>>> >>> Because if the answer is they're being dropped into /etc/security/, >>> I'm going to complain. >>> >>> (Not that I expected that to be the answer, but I don't like making >>> assumptions while reading specifications.) >>> >> And we should question every addition to /etc/*. New /etc/* files >> need justification as specified in the ARC SMF policy. >> > > Hello! Please unstrap the jet-engine from this tangent! Jyri's hand-wave > example has nothing to do with this case. Lots of people get upset, and > rightly so, by the ARCs dragging discussions off into directions completely > unrelated to the project at hand, often based on wild speculation or > offhand comments. Let's not do that more than we're forced to. > > The case specifies the actual interfaces exported by the project. If they > went anywhere other than somewhere under /usr/lib/python2.4, they'd be > unusable without special care, which I would hope would be mentioned in the > case materials. In general, that has to be the case, or we'd ask every > project team to give us a complete dump of all the interfaces they used, > interesting or otherwise, and that's far more than we need, unless we have > reason not to trust the project team. > > It probably would be worthwhile to suggest that all cases delivering Python > modules as Public interfaces should import PSARC/2005/555, which they > should be doing. > > Danek > And now for another view...
DISCLAIMER: I'm not sure this is the right example. If the right way to integrate Python Twisted is to make it interact with SFM or Rbac or whatever, then that integration needs to use those facilities. These are the facilities that are (warning: pun approaching) the secret sauce that distinguishes Solaris from the great hoard of Linux Distros (remember Linux only the kernel). Gary said "we should question every addition to /etc/*". That may be a bit of a strong statement, but apply `sed -e "s/question/understand/g" and I be more than comfortable with the statement. All the free software should be modified to use any facilities where using that facility is the "right thing"(tm). Its not just about saying "configure; make; putback". From the materials, I'm not sure I can tell if Python Twisted should be using Solaris databases/facilities. Perhaps we should move this to "waiting needs spec" until those questions can be answered. - jek3 - jek3
