Re: [GnomeMeeting-devel-list] GnomeMeeting in the very near future
- From: Miguel Rodríguez <migrax terra es>
- To: gnomemeeting-devel-list gnome org
- Subject: Re: [GnomeMeeting-devel-list] GnomeMeeting in the very near future
- Date: Tue, 27 Apr 2004 10:05:18 +0200
On Tue, 2004-04-27 at 09:45 +0200, Damien Sandras wrote:
> Le mar, 27/04/2004 à 09:17 +0200, Miguel RodrÃguez a écrit :
> > I don't want to impose anything on anybody. I just feel that developers
> > should be able to use gnome26 features in the cvs version if the next
> > stable version will depend on it.
> >
> > If a user finds it difficult to use the cvs version, then he/she should
> > use the stable version. On the other hand, if he/she feels brave enough
> > to cope with the inherent difficulties in using development code, they
> > are more than welcome to test, report bugs, send patches and so on.
> >
> > Just wanted to clarify my position.
>
> OK, then I will clarify mine.
>
> I perfectly agree with you. We are a GNOME 2.6 application and must make
> an extensive use of GNOME 2.6 features. However, the requirement you
> impose to CVS packagers is a bit excessive because :
> - it only fixes a bug that few people will encounter
> - removing that requirement doesn't remove the feature you added
> - and even if it was removing that feature, it wouldn't be a big loss in
> functionnality
>
So you think the best solution is:
* Do not require gnome-vfs >= 2.6 in configure.in
* and let the bug stay there for those suing earlier version?
Well, I think configure.in should state the real requirements, but I
understand what the problem is. I see two solutions:
a) packagers patch configure.in themselves so they can compile against
gnome-vfs < 2.6
b) we revert the requirement from cvs. But the code to load static
images won't work properly with old gnome-vfs.
I would do a), but can do b) immediately if you feel is the the right
way to proceed.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]