Re: Dependencies

Il ven, 2003-12-12 alle 17:29, Dave Malcolm ha scritto:
> In the past we've had an informal policy of trying to minimise
> Conglomerate's dependencies, restricting things to standard packages
> likely to be found on relatively recent distributions.
> 
> Part of the reason for this was that I had a bad internet connection and
> only had the standard packages myself.

Keep in mind that many users are still limited by a dialup connection
(this is my case, although I have a fast connection at the University).

> Now that I've got bandwidth, I'm building the latest version of GNOME
> from source locally, and I'd like to start pushing things a bit more.  

I agree.

> I've been attempting to support GNOME 2.0, and this is too restrictive,
> with GNOME 2.4 out, and GNOME 2.5 about to go into API freeze for 2.6
> 
> Here are some examples of the things I'd like to do/use:
> - undo/redo drop down combos as seen in Gnumeric

Very nice.

> - action-based GUI API, which should make it easier to do a big overhaul
> of the menus and toolbars, which there was some discussion of a while
> back

Yes!

> - recent files to appear in the File menu

Yes! :)

> - libgsf for loading/saving
> - the new xml loading and saving APIs
> - Gnome Office plugin system
> - the new file selector to be properly integrated into the app

This is the only one I have doubts about.

> - probably more examples (please suggest them!)
> 
> I'd also like to chop out some of conglomerate's code and get it merged
> into either GTK or one of the gnome libraries.
> 
> It's becoming a pain to maintain the code using the old GNOME 2.0
> features, especially when there are much easier ways to do certain
> things in the newer APIs.
> 
> So the question is:  how much pain would it cause people if Conglomerate
> started requiring more recent versions of Gnome/GTK etc?  Potentially
> very recent ones?

AFAIC, no pain at all requiring the latest *stable* releases, could be a
little painful to require devel ones: wrt to the new file requester,
f.i., one should upgrade to the latest GTK+ libs, which could be unwise
in a production environment.

If you stay on the bleeding edge, you'll also risk to lose beta testers
(not everyone has a spare partition/box to play with experimental
stuff).

> Some questions:  
> - What versions of these packages have you got installed?

gtk+ 2.2.4
gnome 2.4
  
> - Are you building Conglomerate on top of the GNOME that came with your
> distribution, or on top of a locally-built version of some kind?

Actually, I'm not building Conglomerate at all: good old Götz Waschk
uploads an RPM packet in Mandrake Linux contrib 24-48 hours after every
new release (thanks Götz! :)

> - What's in the various versions of Debian?
> - What's other distributions are you using, and what versions of GNOME
> do they use?
> - Can we can get away with GNOME 2.2?  
> - Ditto for GNOME 2.4?  
> - Ditto for GNOME 2.5?
> - Ditto for Latest CVS?

Er ... see above. Personally, I wouldn't keep up with development.

> - Does anyone use GARNOME; would it be OK to track what's in GARNOME?
> - Ditto for any other build scripts?  (I'm using jhbuild)

I tried to use those, but they really require a permanent connection to
the net.

My 0.2 € cents, let's hear from other people.

Ciao

-- 
 
Roberto Rosselli Del Turco	roberto.rossellidelturco at unito.it
Dipartimento di Scienze		rosselli at ling.unipi.it
del Linguaggio			Then spoke the thunder	DA
Universita' di Torino		Datta: what have we given?  (TSE)
 
  Hige sceal the heardra,     heorte the cenre,
  mod sceal the mare,       the ure maegen litlath.  (Maldon 312-3)