Am 05.06.2018 um 23:41 schrieb Peter Kovacs:
> We have decided this without considering that gstreamer gstreamer 1.0.0 can 
> not compile there.
> I am not sure, if we compile gstreamer with Damjan's symbol patch. Will it 
> the work despite gstreamer has to be build with a different gcc Version? (I 
> lack the experience on this, but my expectation is that it will cause issues)
>
> So I would like to change my mind to switch directly to 7. And resolve issues 
> with 6 seperatly. If we find volunteers for it.
> I am not sure if it is worth to invest much in centos6 with the current 
> volunteers we have. (Despite the fact that the interest or time seems not to 
> fit.)

Personally, I have no use for gstreamer... ;-)

But I would be happy to have a 4.2.0-dev

 - without general error on Linux [1]
 - without crash when inserting a frame in Writer (cross platform) [2]
 - with the ability to open ppt files with a double click on Windows [3]

Shouldn't we concentrate on release blockers like these? There is enough
work to do before we can even think about releasing a beta.

Regards,
   Matthias

[1] https://bz.apache.org/ooo/show_bug.cgi?id=127315
[2] https://bz.apache.org/ooo/show_bug.cgi?id=125129
[3] https://bz.apache.org/ooo/show_bug.cgi?id=127783

>
>
> Am 5. Juni 2018 23:31:38 MESZ schrieb Matthias Seidel 
> <matthias.sei...@hamburg.de>:
>> Am 05.06.2018 um 23:26 schrieb Marcus:
>>> Am 05.06.2018 um 00:15 schrieb Kay Schenk:
>>>> On Mon, Jun 4, 2018 at 12:09 PM, Jim Jagielski <j...@jagunet.com>
>> wrote:
>>>>> I am setup to be able to provide both CentOS5 Linux builds, for
>> "old"
>>>>> systems (and gstreamer 0.10), and Ubuntu-or-CentOS6 Linux builds
>> for
>>>>> newer
>>>>> ones (and gstreamer 1.x), so if that is the decision, that's fine
>> w/
>>>>> me. It
>>>>> increases, substantially, the total volume of releases we need to
>>>>> do, which
>>>>> is a factor, so we need to make sure our distro channel is aware.
>>>>>
>>>> ​I think we'd need to go up to CentOS7 for gstreamer 1.x.
>> Anyway...point
>>>> taken.
>>> CentOS5 is done [1]. We can try to upgrade to CentOS6 as our new base
>>> platform. Or do some effort to jump directly to CentOS7.
>> We already decided to build 4.2.0 and later with CentOS6:
>> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_6_for_AOO_4.2.x_and_later
>>
>> Regards,
>>    Matthias
>>
>>> [1] https://en.wikipedia.org/wiki/CentOS#End-of-support_schedule
>>>
>>> Marcus
>>>
>>>
>>>
>>>>> I just don't like the one "making" that decision... but that's the
>> only
>>>>> one I'm qualified to make since that's the only one I'm qualified
>> to
>>>>> adjust
>>>>> trunk to represent (that is, pull the gstreamer-0.10 stuff from
>>>>> 4.1.5 and
>>>>> reincorporate it into trunk to exist in parallel w/ the new
>>>>> gstreamer-1.x
>>>>> stuff in there now).
>>>>>
>>>>> FWIW, our inability to follow-through on this single issue is quite
>>>>> bothersome to me...
>>>>
>>>>>> On May 30, 2018, at 6:19 PM, Torokhov Sergey
>> <torokhov-...@yandex.ru>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> 29.05.2018, 21:30, "Jim Jagielski" <j...@jagunet.com>:
>>>>>>> I think the hope is to continue using CentOS5 for our official
>> AOO
>>>>> community builds. If not, then this becomes much easier, but it is,
>>>>> IMO, a
>>>>> major policy decision to do that. recall that gstreamer-1.x is
>>>>> incompatible
>>>>> w/ CentOS5.
>>>>>>> I have no idea how to do #2 but #1 looks like simple brute force.
>>>>> Certainly not elegant but if that's what it takes to get past this
>>>>> holding
>>>>> pattern, then that's what we have to do.
>>>>>> Some packages provides builds both for old and new systems.
>>>>>> E.g. here ( https://www.onlyoffice.com/en/download-desktop.aspx )
>>>>> presented
>>>>>> packages both for old Debian and Ubuntu (Debian 7, Ubuntu 12.04 )
>> and
>>>>> their new releases (Debian 8, Ubuntu 14.04, 16.04, 18.04 ).
>>>>>> Could it be a solution to prepare separate packages?
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to