Re: profterm's eel usage ...

This sounds like "libwnck" all over again - code gets copied and pasted to
multiple places, and even if it doesn't get editied is a pain an
uneccessary duplication. And tends to create "intermediate" libraries that
then don't get any real promises of stability either. I think the options
really are:

	* get eel to the point where it is just a normal stable libarry so
	  people don't have much qualms on depending on it

	* create a library called "proto-gnome" into which code can be
	  moved from other upstream libraries under a review and a promise
	  to move the code into libgngnome{ui} at the next api addition
	  round. Would need to be discouraged to be used by anything but
	  gnome components so is a bit painful.

I guess it would be possible to have another "desktop" gnome library but I
don't have faith in that.

On 23 Feb 2002, Havoc Pennington wrote:

> Michael Meeks <michael ximian com> writes:
> > 
> > 	May I ask - why are you cutting and pasting eel code into profterm ?
> > profterm is in the core platform modules, at the same level as eel, and
> > surely could simply depend on eel ?
> > 
> > 	What is the thinking there ?
> > 
> Unstable libs are a big pain, from my point of view. They cause a lot
> of packaging headaches. Moreover eel is large, and I only want one
> feature, which is the ellipsizing label. We also want the ellipsizing
> label in tasklist and several other places, and making all those
> depend on eel would suck. So I don't want to set the trend of
> depending on eel in order to get the ellipsizing label.
> It's an automated cut-and-paste; there are no changes to eel code and
> there's a makefile target to update to latest eel code.
> Also I intend to dump the eel dependency as soon as I can get the
> ellipsizing label somewhere more sensible, and I don't like churn in
> the dependency graph, so a temporary dependency is unattractive.
> Havoc


	I see a dark sail on the horizon
	Set under a dark cloud that hides the sun
	Bring me my Broadsword and clear understanding

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]