#26717: tint2 @0.11 Submission -------------------------------------+-------------------------------------- Reporter: pope@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: tint2 panel taskbar x11 | Port: tint2 -------------------------------------+-------------------------------------- Comment(by ryandesign@…): The cairo, pango and glib2 dependencies should be rewritten to allow their -devel counterparts to satisfy them. See any other port that depends on cairo, pango or glib2 for an example. In fact, the cairo and glib2 dependencies can probably be dropped since pango already depends on them. The same may be true for some of the xorg dependencies. The "revision 0" line can be dropped. Where did the patchfile come from? -- Ticket URL: <https://trac.macports.org/ticket/26717#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

#26717: tint2 @0.11 Submission -------------------------------------+-------------------------------------- Reporter: pope@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: tint2 panel taskbar x11 | Port: tint2 -------------------------------------+-------------------------------------- Comment(by ryandesign@…): My concern with the patchfile was not licensing (though that's a reasonable concern too), but rather that we generally want to provide the same software the developer provided. If the software the developer provided does not work (either at all or specifically on the Mac) and patches are needed, we would of course want those patches sent back to the developer for incorporation into the next version; I wanted to know whether that was the case here. Or sometimes the developer will already have fixed some problem in their repository, and we will want to take that fix as a patchfile before the next version is ready. With third-party modifications that are not incorporated upstream, we would want to fully understand why upstream has not incorporated that code before considering including it in MacPorts. -- Ticket URL: <https://trac.macports.org/ticket/26717#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS