Thx. Yeah, I got that. I also understand that GIO is, by far, the
recommended option.
So our options are:
1. We stick w/ CentOS5 as our ref build system for 4.2.0 but force
Gnome VFS.
2. We move to CentOS6, accept the default of GIO but understand that
this moves CentOS5 as a non-supported OS for our community builds.
3. Just as we offer Linux 32 and 64bit builds, starting w/ 4.2.0
we offer CentOS5 community builds (w/ Gnome VFS) IN ADDITION
TO CentOS6 builds (w/ GIO). (i.e.: 32bit-Gnome VFS, 64bit-Gnome VFS,
32bit-GIO, 64bit-GIO).
It doesn't matter to me... I'm setup to be able to
do any and all options re: builds. Whatever makes most
sense for our end-users and community is what we should
do.
> On Dec 3, 2017, at 6:43 PM, Damjan Jovanovic <[email protected]> wrote:
>
> Sorry what I meant to say was, those flags to ./configure still let you
> build with Gnome VFS instead of GIO.
>
> I didn't take GIO out of the build, I just switched the default VFS
> implementation from Gnome VFS to GIO.
>
> Damjan
>
> On Sun, Dec 3, 2017 at 4:28 PM, Jim Jagielski <[email protected]> wrote:
>
>>
>>> On Dec 3, 2017, at 1:16 AM, Damjan Jovanovic <[email protected]> wrote:
>>>
>>> On Sun, Dec 3, 2017 at 2:25 AM, Jim Jagielski <[email protected]> wrote:
>>>
>>>>
>>>>> On Dec 2, 2017, at 5:56 PM, Andrea Pescetti <[email protected]>
>> wrote:
>>>>>
>>>>> On 30/11/2017 Jim Jagielski wrote:
>>>>>> I think for 4.2.x and later, we have deprecated CentOS5 as a supported
>>>>>> build system... I ran into a LOT of issues.
>>>>>
>>>>> Such as, for example?
>>>>
>>>> for starters:
>>>> o zip 3.0.
>>>> o GIO
>>>>
>>>>
>>> If you *really* need GIO, try adding --disable-gio --enable-gnome-vfs to
>>> ./configure.
>>>
>>
>> The issue is that CentOS5 simply does not and can not provide GIO.
>> So it is, IMO at least, unsuitable for our reference community
>> build platform.
>>
>> This was brought up on the "AOO 4.2.0-dev builds" thread.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
