pkgsrc-Changes archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: CVS commit: pkgsrc/devel/glib2

On Tue, Apr 19, 2011 at 04:45:38PM +0100, Roy Marples wrote:
> On 19/04/2011 16:25, Alistair Crooks wrote:
> >On Tue, Apr 19, 2011 at 06:14:03AM +0000, Roy Marples wrote:
> >>Module Name:        pkgsrc
> >>Committed By:       roy
> >>Date:               Tue Apr 19 06:14:02 UTC 2011
> >>
> >>Modified Files:
> >>    pkgsrc/devel/glib2: Makefile
> >>
> >>Log Message:
> >>gtester-report requires python.
> >
> >Well...
> >
> >I've seen the other discussion about "developer laziness", but I don't
> >buy into it that much.  This now means that every glib2 installation
> >requires that we have python installed, for one glib2 function called
> >"gtester-report". glib2 is a common pre-req, and maybe even for smaller,
> >embedded class machines, and I'm not sure a python interpreter is
> >wanted, needed, desirable or useful on such a machine.
> >
> >Where do we draw the line? What pre-reqs should we require for a
> >package just because we can?
> This is a very good question.
> On the one hand we have Thomas saying "just add the dependency" instead 
> of removing an already installed and broken feature and on the other 
> hand we have you saying otherwise.
> I think I side with Thomas on the whole as it's more "correct".
> If someone dislikes the dependency enough, they can split it off into 
> another package or depend on it via an option.

Let's discuss the embedded system, then, since there's a fairly high
probability that glib2 will be installed on it.  Is there a good
reason there's now a python interpreter shipped with it?  I'm not sure
"developer laziness" or "more correct" are good enough reasons for me,
which make up for the increased space required, or functionality to

There must be a reason that dhcpcd-ui is shipped as a different part
of the system to dhcpcd, to take one very useful utility at random
(well, almost).

But, yes, if we absolutely, unarguably, non-negotiably need a python
interpreter as an intrinsic, atomic, inherent part of glib2, let's
ship it.  What is the glib2 piece (i.e.  the user library piece) that
needs this in order to function?


Home | Main Index | Thread Index | Old Index