Sebastien Roy wrote: > Hi Erik, > > On Fri, 2009-05-29 at 11:05 -0700, Erik Lafever wrote: > >> Sebastien Roy wrote: >> >>> It looks like this project makes no backward incompatible changes to any >>> existing software. As such, Minor binding seems unnecessarily >>> restrictive. Why not Patch? >>> > > Any thoughts on this? > I followed the binding type that was used for SUNWlogilab-common and SUNWlogilab-astng which SUNWpylint depends on. I was trying to keep things consistent so I matched what was there.
Thanks, -Erik > >>> It appears that the project team has supplied man pages for each of >>> these interfaces in the materials directory (thank you). Of note is the >>> reference to the use of Tcl/Tk by pylint-gui(1), which suggests that >>> there should be some additional related imported interfaces below. >>> >> Tk represents python's standard built in Tkinter interface, not tcl's. >> > > Ah, I see, thanks for clarifying. > > >>> If >>> Tcl/Tk is in fact used to drive the GUI, then what are the GNOME >>> libraries used for? >>> >>> >> The Gnome libraries are a requirement for SUNWlogilab-common. Should we >> leave out >> SUNWgnome-libs and SUNWgnome-python-libs as they are covered by the >> dependencies >> for SUNWlogilab-common? >> > > I'd leave them out, as they should already be imported by those > interfaces that you depend on and are importing directly, yes. I see > you've done that in your updated spec. > > >>> >>> >>>> Imported Interfaces Classification Comment >>>> ------------------- -------------- --------------------------- >>>> SUNWPython Volatile Python interpreter, library >>>> SUNWgnome-libs Volatile GNOME platform libraries >>>> SUNWgnome-python-libs Volatile Python GNOME libraries >>>> SUNWlogilab-common Uncommitted Python library >>>> SUNWlogilab-astng Uncommitted Python library >>>> >>>> >>> I don't see the latter two packages in the existing repositories. Are >>> they in fact being delivered by this case (and should therefore be part >>> of the exported interfaces), or being delivered by a separate case (if >>> so there is case dependency that should be called out)? >>> >>> >> SUNWlogilab-common and SUNWlogilab-astng are separate cases: >> SUNWlogilab-common http://sac.sfbay/arc/LSARC/2009/298/ >> SUNWlogilab-astng >> http://sac.sfbay/arc/LSARC/2009/299/ >> > > Great, thanks for clarifying that. > > +1 from me, modulo the clarification regarding release binding. > > -Seb > > >