Re: gstreamer status for 4.2.0-dev?

[Jim Jagielski]

Just a FYI that CentOS7 does not "officially" support 32bit. It does provide an 
install image, but there isn't even an EPEL repo for it.

So far, this hasn't been an issue w/ building 4.2.0-dev

> On Jul 4, 2018, at 11:39 PM, Andrea Pescetti  wrote:
> 
> On 03/07/2018 Jim Jagielski wrote:
>> +1. I'll start on a CentOS7 VM.
> 
> Makes sense to me. So our indication for the Release Notes would be something 
> like "OpenOffice 4.2.0 is built on CentOS 7 and is expected to run on 
> Linux-based systems released in YEAR or later (CentOS 7, Ubuntu XYZ...)".
> 
> I'll check versions of glibc and the "YEAR" and "XYZ" placeholders above when 
> I have time. We might also conclude that an Ubuntu LTS version is the best 
> choice, but honestly CentOS 7 should definitely be "old enough" these days.
> 
>> BTW, up to now I've been using VMware Fusion, but will likely start using 
>> Vbox instead... I'm assuming most people are using that anyway and it would 
>> be nice to be able to share the VMs with others.
> 
> I use KVM images. But indeed it's a wise idea to have something that we can 
> share, and I believe Vbox images can be converted for use in KVM. I've done 
> it in the past if I recall correctly.
> 
> Regards,
>  Andrea.
> 
> -
> 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

Re: gstreamer status for 4.2.0-dev?

[Andrea Pescetti]

On 03/07/2018 Jim Jagielski wrote:

+1. I'll start on a CentOS7 VM.


Makes sense to me. So our indication for the Release Notes would be 
something like "OpenOffice 4.2.0 is built on CentOS 7 and is expected to 
run on Linux-based systems released in YEAR or later (CentOS 7, Ubuntu 
XYZ...)".


I'll check versions of glibc and the "YEAR" and "XYZ" placeholders above 
when I have time. We might also conclude that an Ubuntu LTS version is 
the best choice, but honestly CentOS 7 should definitely be "old enough" 
these days.



BTW, up to now I've been using VMware Fusion, but will likely start using Vbox 
instead... I'm assuming most people are using that anyway and it would be nice 
to be able to share the VMs with others.


I use KVM images. But indeed it's a wise idea to have something that we 
can share, and I believe Vbox images can be converted for use in KVM. 
I've done it in the past if I recall correctly.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Jim Jagielski]

+1. I'll start on a CentOS7 VM.

BTW, up to now I've been using VMware Fusion, but will likely start using Vbox 
instead... I'm assuming most people are using that anyway and it would be nice 
to be able to share the VMs with others.

> On Jul 3, 2018, at 8:30 AM, Peter Kovacs  wrote:
> 
> I think there was no big support for supporting gstreamer 0.1.0 on 4.2. 
> branch. If those who need it , they should help.
> Also I think it makes more sense in such a case to keep maintenance for 4.1.x 
> branch.
> 
> That means we will have to move to centOS7 for building.
> 
> 
> 
> On 03.07.2018 14:00, Jim Jagielski wrote:
>> Oops. Forget that. Even CentOS6 doesn't support gstreamer-1.0.
>> 
>> 
>>> On Jul 3, 2018, at 6:47 AM, Jim Jagielski  wrote:
>>> 
>>> So have we come up w/ an agreed upon decision? Are we baselining
>>> gstreamer-1.0, and our community/build-systems will be based on
>>> CentOS6 (ie: dropping "official" support for CentOS5)?
>>> 
>>> If so, I can start on some 4.2.0-dev r1834788 Linux builds...
>>> 
>>> (I'm already trying macOS builds but having some weird build
>>> issues w/ main/store)
>>> 
>>> -
>>> 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
>> 
> 
> 
> -
> 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

Re: gstreamer status for 4.2.0-dev?

[Peter Kovacs]

I think there was no big support for supporting gstreamer 0.1.0 on 4.2. 
branch. If those who need it , they should help.
Also I think it makes more sense in such a case to keep maintenance for 
4.1.x branch.


That means we will have to move to centOS7 for building.



On 03.07.2018 14:00, Jim Jagielski wrote:

Oops. Forget that. Even CentOS6 doesn't support gstreamer-1.0.



On Jul 3, 2018, at 6:47 AM, Jim Jagielski  wrote:

So have we come up w/ an agreed upon decision? Are we baselining
gstreamer-1.0, and our community/build-systems will be based on
CentOS6 (ie: dropping "official" support for CentOS5)?

If so, I can start on some 4.2.0-dev r1834788 Linux builds...

(I'm already trying macOS builds but having some weird build
issues w/ main/store)

-
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




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Jim Jagielski]

Oops. Forget that. Even CentOS6 doesn't support gstreamer-1.0.


> On Jul 3, 2018, at 6:47 AM, Jim Jagielski  wrote:
> 
> So have we come up w/ an agreed upon decision? Are we baselining
> gstreamer-1.0, and our community/build-systems will be based on
> CentOS6 (ie: dropping "official" support for CentOS5)?
> 
> If so, I can start on some 4.2.0-dev r1834788 Linux builds...
> 
> (I'm already trying macOS builds but having some weird build
> issues w/ main/store)
> 
> -
> 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

Re: gstreamer status for 4.2.0-dev?

[Jim Jagielski]

So have we come up w/ an agreed upon decision? Are we baselining
gstreamer-1.0, and our community/build-systems will be based on
CentOS6 (ie: dropping "official" support for CentOS5)?

If so, I can start on some 4.2.0-dev r1834788 Linux builds...

(I'm already trying macOS builds but having some weird build
issues w/ main/store)

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Peter kovacs]

After some thinkibg, I agree with Dave. The Distributions affeced should help 
in supporting the backward compability. We can support and guide through the 
process.
If we find volunteers it could be a small step back into stronger Linux 
Distribution support. If no one is interested it saves us complexity, which is 
also fine.

It would be cool if we write a blog post. We could attach a Forum thread for 
discussion.
Plus a reach out post to the affected distributions. (I think centOS6 is the 
only version affected , but I am not sure.)

I try to make time until weekend for a first blog post draft, if we agree on 
this.

Am 6. Juni 2018 19:21:10 MESZ schrieb Jim Jagielski :
>Let's not focus on CentOS5 vs CentOS6 for now... the issue is that
>gstreamer-1.0 requires that previously supported Linux OSs and
>platforms will no longer be supported; that is, our community builds
>will no longer work for them.
>
>Are we OK with that?
>
>That is the main consideration. Everything else is determined from that
>decision.
>
>So what say we all?
>
>> On Jun 5, 2018, at 5:26 PM, Marcus  wrote:
>> 
>> Am 05.06.2018 um 00:15 schrieb Kay Schenk:
>>> On Mon, Jun 4, 2018 at 12:09 PM, Jim Jagielski 
>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.
>> 
>> [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
>
 wrote:
> 
> 
> 
> 29.05.2018, 21:30, "Jim Jagielski" :
>> 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

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Marcus]

Am 06.06.2018 um 21:37 schrieb Jim Jagielski:




On Jun 6, 2018, at 3:21 PM, Marcus  wrote:

Am 06.06.2018 um 19:21 schrieb Jim Jagielski:

Let's not focus on CentOS5 vs CentOS6 for now... the issue is that 
gstreamer-1.0 requires that previously supported Linux OSs and platforms will 
no longer be supported; that is, our community builds will no longer work for 
them.


sure, it's about the platform we now need to use. When gstreamer is no longer 
working with the old CentOS5 system, then let's update it.

That's what I want to express, not more or less.



No, it's about what platforms we now provide community binaries for.


I think we talk about the same thing but don't understand each other. 
;-) OK, let's go on.



To be explicit: With the jump to 4.2.x, we will no longer be supporting older Linux 
platforms that we DID support w/ 4.1.x. This is all about what we change regarding what 
platforms we provide community builds for (and thus "officially" support). If 
we say that all Linux platforms that are too old to use gstreamer-1.x (eg: CentOS5, but 
actually it's a kernel dependency) are no longer officially supported, GREAT. But let's 
just make sure that is our decision.

I actually thought one of the considerations of this project was to support as 
many older platforms as possible... if that is NOT the case, then again, we 
need to make that decision explicitly. WHAT is our backwards 
compatibility/support roadmap for 4.2.x??


Yes, "as possible". But when our effort is somewhen to high to support 
the older things, then move on and leave them behind us. Mostly the 
vendor has already given up much earlier. ;-)


But as I'm not a developer I cannot estimate how difficult it is to go 
on as it is today.


Marcus


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Jim Jagielski]

> On Jun 6, 2018, at 3:21 PM, Marcus  wrote:
> 
> Am 06.06.2018 um 19:21 schrieb Jim Jagielski:
>> Let's not focus on CentOS5 vs CentOS6 for now... the issue is that 
>> gstreamer-1.0 requires that previously supported Linux OSs and platforms 
>> will no longer be supported; that is, our community builds will no longer 
>> work for them.
> 
> sure, it's about the platform we now need to use. When gstreamer is no longer 
> working with the old CentOS5 system, then let's update it.
> 
> That's what I want to express, not more or less.
> 

No, it's about what platforms we now provide community binaries for.

To be explicit: With the jump to 4.2.x, we will no longer be supporting older 
Linux platforms that we DID support w/ 4.1.x. This is all about what we change 
regarding what platforms we provide community builds for (and thus "officially" 
support). If we say that all Linux platforms that are too old to use 
gstreamer-1.x (eg: CentOS5, but actually it's a kernel dependency) are no 
longer officially supported, GREAT. But let's just make sure that is our 
decision.

I actually thought one of the considerations of this project was to support as 
many older platforms as possible... if that is NOT the case, then again, we 
need to make that decision explicitly. WHAT is our backwards 
compatibility/support roadmap for 4.2.x??


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Marcus]

Am 06.06.2018 um 19:21 schrieb Jim Jagielski:

Let's not focus on CentOS5 vs CentOS6 for now... the issue is that 
gstreamer-1.0 requires that previously supported Linux OSs and platforms will 
no longer be supported; that is, our community builds will no longer work for 
them.


sure, it's about the platform we now need to use. When gstreamer is no 
longer working with the old CentOS5 system, then let's update it.


That's what I want to express, not more or less.


Are we OK with that?

That is the main consideration. Everything else is determined from that 
decision.

So what say we all?


IMHO Dave had the perfect answer: When someone else needs the old stuff, 
then they are free to do the work and deliver patches. (correspondingly)


Marcus




On Jun 5, 2018, at 5:26 PM, Marcus  wrote:

Am 05.06.2018 um 00:15 schrieb Kay Schenk:

On Mon, Jun 4, 2018 at 12:09 PM, Jim Jagielski  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.

[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 

wrote:




29.05.2018, 21:30, "Jim Jagielski" :

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

Re: gstreamer status for 4.2.0-dev?

[Jim Jagielski]

Let's not focus on CentOS5 vs CentOS6 for now... the issue is that 
gstreamer-1.0 requires that previously supported Linux OSs and platforms will 
no longer be supported; that is, our community builds will no longer work for 
them.

Are we OK with that?

That is the main consideration. Everything else is determined from that 
decision.

So what say we all?

> On Jun 5, 2018, at 5:26 PM, Marcus  wrote:
> 
> Am 05.06.2018 um 00:15 schrieb Kay Schenk:
>> On Mon, Jun 4, 2018 at 12:09 PM, Jim Jagielski  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.
> 
> [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 
>>> wrote:
 
 
 
 29.05.2018, 21:30, "Jim Jagielski" :
> 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

Re: gstreamer status for 4.2.0-dev?

[Jim Jagielski]

> On Jun 4, 2018, at 6:15 PM, Kay Schenk  wrote:
> 
> ​I think we'd need to go up to CentOS7 for gstreamer 1.x. Anyway...point
> taken.

Hmmm... I seem to recall it building on CentOS6. I could be mistaken ;)

Re: gstreamer status for 4.2.0-dev?

[Peter kovacs]

That's why the simplest solution is to move to centOS7 for now. We need to 
debug the gstreamer support too.
Even if it is not important to all users /devs.


Am 6. Juni 2018 00:03:56 MESZ schrieb Matthias Seidel 
:
>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
>:
>>> 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 
>>> 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
>>> 
>> wrote:
>>>
>>>
>>> 29.05.2018, 21:30, "Jim Jagielski" :
 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
>>

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Matthias Seidel]

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 
> :
>> 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 
>> 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
>> 
> wrote:
>>
>>
>> 29.05.2018, 21:30, "Jim Jagielski" :
>>> 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
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: gstreamer status for 4.2.0-dev?

[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.)


Am 5. Juni 2018 23:31:38 MESZ schrieb Matthias Seidel 
:
>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 
>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
>
 wrote:
>
>
>
> 29.05.2018, 21:30, "Jim Jagielski" :
>> 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

Re: gstreamer status for 4.2.0-dev?

[Matthias Seidel]

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  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 
>>> wrote:



 29.05.2018, 21:30, "Jim Jagielski" :
> 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
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: gstreamer status for 4.2.0-dev?

[Marcus]

Am 05.06.2018 um 08:14 schrieb Dave Fisher:

Those who need to support older versions of Centos with newer versions of 
Openoffice should come forward and do the work!


also a valid argument. ;-)

Marcus




On Jun 4, 2018, at 10:59 PM, Peter Kovacs  wrote:

How about we ask the community if we need to support centOS6?
If no one uses CentOS6 maybe we make a fuzz for nothing. I am not aware that 
another distro is using that old versions.

The important thing is how much users we say we need to extend the support to 
CentOS 6?

I would also include the symbolic patch that Damjan provided. So we can build 
gstreamer support in general, but do not have to deliver it.

Am 4. Juni 2018 21:09:52 MESZ schrieb Jim Jagielski :

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 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 

wrote:




29.05.2018, 21:30, "Jim Jagielski" :

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

Re: gstreamer status for 4.2.0-dev?

[Marcus]

Am 05.06.2018 um 00:15 schrieb Kay Schenk:

On Mon, Jun 4, 2018 at 12:09 PM, Jim Jagielski  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.


[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 

wrote:




29.05.2018, 21:30, "Jim Jagielski" :

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

Re: gstreamer status for 4.2.0-dev?

[Dave Fisher]

Those who need to support older versions of Centos with newer versions of 
Openoffice should come forward and do the work!

Sent from my iPhone

> On Jun 4, 2018, at 10:59 PM, Peter Kovacs  wrote:
> 
> How about we ask the community if we need to support centOS6?
> If no one uses CentOS6 maybe we make a fuzz for nothing. I am not aware that 
> another distro is using that old versions.
> 
> The important thing is how much users we say we need to extend the support to 
> CentOS 6?
> 
> I would also include the symbolic patch that Damjan provided. So we can build 
> gstreamer support in general, but do not have to deliver it.
> 
> Am 4. Juni 2018 21:09:52 MESZ schrieb Jim Jagielski :
>> 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 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 
>> wrote:
>>> 
>>> 
>>> 
>>> 29.05.2018, 21:30, "Jim Jagielski" :
 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
> 
> -
> 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

Re: gstreamer status for 4.2.0-dev?

[Peter Kovacs]

How about we ask the community if we need to support centOS6?
If no one uses CentOS6 maybe we make a fuzz for nothing. I am not aware that 
another distro is using that old versions.

The important thing is how much users we say we need to extend the support to 
CentOS 6?

I would also include the symbolic patch that Damjan provided. So we can build 
gstreamer support in general, but do not have to deliver it.

Am 4. Juni 2018 21:09:52 MESZ schrieb Jim Jagielski :
>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 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 
>wrote:
>> 
>> 
>> 
>> 29.05.2018, 21:30, "Jim Jagielski" :
>>> 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

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Kay Schenk]

On Mon, Jun 4, 2018 at 12:09 PM, Jim Jagielski  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.
​


>
> 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 
> wrote:
> >
> >
> >
> > 29.05.2018, 21:30, "Jim Jagielski" :
> >> 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
>
>


-- 
--
MzK

"Less is MORE."

Re: gstreamer status for 4.2.0-dev?

[Jim Jagielski]

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 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  wrote:
> 
> 
> 
> 29.05.2018, 21:30, "Jim Jagielski" :
>> 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

Re: gstreamer status for 4.2.0-dev?

[Kay Schenk]

On 05/30/2018 03:08 PM, Torokhov Sergey wrote:
>
> 28.05.2018, 20:19, "Kay Schenk" :
>
>> This is ONLY for Linux. So, how is multimedia "integrated" in AOO for
>> Mac and Windows? Can someone point us to the applicable code areas for this?
>>
>> I have a feeling gstreamer was integrated long ago when no other
>> multi-media standard/app for Linux existed. Now it seems VLC seems to
>> the standard for the most part. (This is a dated web page but I think
>> it's still a good reference:
>> http://www.yolinux.com/TUTORIALS/LinuxTutorialMimeTypesAndApplications.html).
>> Basically, we are supplying gstreamer as a multimedia app to Linux when
>> maybe this isn't really needed.
> The using of gstreamer multimedia backend of OpenOffice was anounced in 
> Oracle OpenOffice.org 3.4 Beta 
> in April 2010 and the first release with it was the Apache OpenOffice 3.4.0 
> in May 2012.
>
> Previously to play multimedia content in OpenOffice the Java Media Framework 
> (JMF) was used
> ( https://wiki.openoffice.org/wiki/Java/Java_Media_Framework ). 
> The JMF wasn't updated since 2003 and supported too small amount of formats 
> in contrast to gstreamer.

Thank you for this information, it is useful. I understand the need for
a standardized AV app in some ways, but, assuming an end user's
preferred AV app supports a wide variety of formats, I think it would be
better for AOO (in non-Win, non-Mac) implementations to try to determine
the the end user's AV application, and use that rather than providing a
new AV app. But...a much longer discussion not on this thread.


-- 
--
MzK

"Less is MORE."


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Torokhov Sergey]

29.05.2018, 21:30, "Jim Jagielski" :
> 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

Re: gstreamer status for 4.2.0-dev?

[Torokhov Sergey]

28.05.2018, 20:19, "Kay Schenk" :

> This is ONLY for Linux. So, how is multimedia "integrated" in AOO for
> Mac and Windows? Can someone point us to the applicable code areas for this?
>
> I have a feeling gstreamer was integrated long ago when no other
> multi-media standard/app for Linux existed. Now it seems VLC seems to
> the standard for the most part. (This is a dated web page but I think
> it's still a good reference:
> http://www.yolinux.com/TUTORIALS/LinuxTutorialMimeTypesAndApplications.html).
> Basically, we are supplying gstreamer as a multimedia app to Linux when
> maybe this isn't really needed.

The using of gstreamer multimedia backend of OpenOffice was anounced in Oracle 
OpenOffice.org 3.4 Beta 
in April 2010 and the first release with it was the Apache OpenOffice 3.4.0 in 
May 2012.

Previously to play multimedia content in OpenOffice the Java Media Framework 
(JMF) was used
( https://wiki.openoffice.org/wiki/Java/Java_Media_Framework ). 
The JMF wasn't updated since 2003 and supported too small amount of formats in 
contrast to gstreamer.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Jim Jagielski]

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.

> On May 28, 2018, at 3:12 AM, Damjan Jovanovic  wrote:
> 
> 3. Build on a newer CentOS or other distro.
> 4. Link to 1.0.0 using run-time dynamic linking, using that patch I made,
> and only require the gstreamer-1.0.0 tarball at compile time to find the
> headers.
> 
> Damjan
> 
> On Mon, May 28, 2018 at 9:06 AM Peter kovacs  wrote:
> 
>> Imho the gstreamer libs are still the method of choice for doing
>> multimedia.
>> 
>> The current state is that trunk can utilize the gstreamer API 1.0.0
>> 
>> We have the issue not resolved the issue to provide gstreamer for
>> different Distributions. (Main issue: centos6 is to old to support the new
>> gstreamer 1.0.0 API)
>> We have 2 suggestions to solve the issue:
>> 1) implement 0.1.0 and 1.0.0 API.
>> 2) move the implementation into an optional extention.
>> 
>> Both solutions have currently not followed up.
>> 
>> All the best
>> Peter
>> 
>> Am 26. Mai 2018 18:53:46 MESZ schrieb Kay Schenk :
>>> On 05/23/2018 05:35 AM, Jim Jagielski wrote:
 Subj line sez it all... where are we? There was a proposal to make it
>>> a run-time dependency but afaict there hasn't been any effort yet it
>>> doing that.
 
 I know we have a handful of other things TODO re: 4.2.0 but this
>>> seems to be an inflection point for the Linux builds and so I really
>>> think we need to resolve this if we have any intent in getting a 4.2.0
>>> beta out in a reasonable time frame.
>>> 
>>> What would happen if we simply stopped including the --with-gstreamer
>>> option in the build? Mac and Windows builds don't use it, and it only
>>> applies to Linux.
>>> 
>>> I haven't investigated the code much to see how the gstreamer libraries
>>> are used. The Linux distros now mostly use Freedesktop lower level
>>> interfaces except I don't know what Unity uses. Is building with
>>> gstreamer still needed/compliant with this? In short, how are video
>>> applications determined in Linux now? Do we need a different approach
>>> for integration of video objects in Linux?
>>> 
>>> If anyone knows the history of this, it would be very helpful to this
>>> discussion.
>> 
>> -
>> 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

Re: gstreamer status for 4.2.0-dev?

[Jim Jagielski]

> On May 28, 2018, at 3:05 AM, Peter kovacs  wrote:
> 
> Imho the gstreamer libs are still the method of choice for doing multimedia.
> 
> The current state is that trunk can utilize the gstreamer API 1.0.0
> 
> We have the issue not resolved the issue to provide gstreamer for different 
> Distributions. (Main issue: centos6 is to old to support the new gstreamer 
> 1.0.0 API)
> We have 2 suggestions to solve the issue:
> 1) implement 0.1.0 and 1.0.0 API. 
> 2) move the implementation into an optional extention.
> 
> Both solutions have currently not followed up. 
> 

Is anyone able to follow up on these? #2 seems the wiser choice.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Kay Schenk]

Thanks Peter. I will investigate.

___
Sent from MzK's phone.

On Mon, May 28, 2018, 10:54 Peter Kovacs  wrote:

> The implementation can be found at avmedia/source/
>
> I think we use native API / libs for Windows and Mac.
>
>
> Am 28. Mai 2018 19:18:34 MESZ schrieb Kay Schenk :
> >On 05/28/2018 12:05 AM, Peter kovacs wrote:
> >> Imho the gstreamer libs are still the method of choice for doing
> >multimedia.
> >
> >This is ONLY for Linux. So, how is multimedia "integrated" in AOO for
> >Mac and Windows? Can someone point us to the applicable code areas for
> >this?
> >
> >I have a feeling gstreamer was integrated long ago when no other
> >multi-media standard/app for Linux existed. Now it seems VLC seems to
> >the standard for the most part. (This is a dated web page but I think
> >it's still a good reference:
> >
> http://www.yolinux.com/TUTORIALS/LinuxTutorialMimeTypesAndApplications.html
> ).
> >Basically, we are supplying gstreamer as a multimedia app to Linux when
> >maybe this isn't really needed.
> >
> >>
> >> The current state is that trunk can utilize the gstreamer API 1.0.0
> >>
> >> We have the issue not resolved the issue to provide gstreamer for
> >different Distributions. (Main issue: centos6 is to old to support the
> >new gstreamer 1.0.0 API)
> >> We have 2 suggestions to solve the issue:
> >> 1) implement 0.1.0 and 1.0.0 API.
> >> 2) move the implementation into an optional extention.
> >>
> >> Both solutions have currently not followed up.
> >>
> >> All the best
> >> Peter
> >>
> >> Am 26. Mai 2018 18:53:46 MESZ schrieb Kay Schenk
> >:
> >>> On 05/23/2018 05:35 AM, Jim Jagielski wrote:
>  Subj line sez it all... where are we? There was a proposal to make
> >it
> >>> a run-time dependency but afaict there hasn't been any effort yet it
> >>> doing that.
>  I know we have a handful of other things TODO re: 4.2.0 but this
> >>> seems to be an inflection point for the Linux builds and so I really
> >>> think we need to resolve this if we have any intent in getting a
> >4.2.0
> >>> beta out in a reasonable time frame.
> >>>
> >>> What would happen if we simply stopped including the
> >--with-gstreamer
> >>> option in the build? Mac and Windows builds don't use it, and it
> >only
> >>> applies to Linux.
> >>>
> >>> I haven't investigated the code much to see how the gstreamer
> >libraries
> >>> are used. The Linux distros now mostly use Freedesktop lower level
> >>> interfaces except I don't know what Unity uses. Is building with
> >>> gstreamer still needed/compliant with this? In short, how are video
> >>> applications determined in Linux now? Do we need a different
> >approach
> >>> for integration of video objects in Linux?
> >>>
> >>> If anyone knows the history of this, it would be very helpful to
> >this
> >>> discussion.
> >> -
> >> 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
>
>

Re: gstreamer status for 4.2.0-dev?

[Damjan Jovanovic]

As I explained in a previous mail, Windows uses DirectShow and Mac uses
QuickTime or MacAVF.

Linux's equivalent of DirectShow is gstreamer. It also builds pipelines of
filters, has codecs, supports embedding into windows, etc.

On Mon, May 28, 2018 at 7:19 PM Kay Schenk  wrote:

> On 05/28/2018 12:05 AM, Peter kovacs wrote:
> > Imho the gstreamer libs are still the method of choice for doing
> multimedia.
>
> This is ONLY for Linux. So, how is multimedia "integrated" in AOO for
> Mac and Windows? Can someone point us to the applicable code areas for
> this?
>
> I have a feeling gstreamer was integrated long ago when no other
> multi-media standard/app for Linux existed. Now it seems VLC seems to
> the standard for the most part. (This is a dated web page but I think
> it's still a good reference:
> http://www.yolinux.com/TUTORIALS/LinuxTutorialMimeTypesAndApplications.html
> ).
> Basically, we are supplying gstreamer as a multimedia app to Linux when
> maybe this isn't really needed.
>
> >
> > The current state is that trunk can utilize the gstreamer API 1.0.0
> >
> > We have the issue not resolved the issue to provide gstreamer for
> different Distributions. (Main issue: centos6 is to old to support the new
> gstreamer 1.0.0 API)
> > We have 2 suggestions to solve the issue:
> > 1) implement 0.1.0 and 1.0.0 API.
> > 2) move the implementation into an optional extention.
> >
> > Both solutions have currently not followed up.
> >
> > All the best
> > Peter
> >
> > Am 26. Mai 2018 18:53:46 MESZ schrieb Kay Schenk :
> >> On 05/23/2018 05:35 AM, Jim Jagielski wrote:
> >>> Subj line sez it all... where are we? There was a proposal to make it
> >> a run-time dependency but afaict there hasn't been any effort yet it
> >> doing that.
> >>> I know we have a handful of other things TODO re: 4.2.0 but this
> >> seems to be an inflection point for the Linux builds and so I really
> >> think we need to resolve this if we have any intent in getting a 4.2.0
> >> beta out in a reasonable time frame.
> >>
> >> What would happen if we simply stopped including the --with-gstreamer
> >> option in the build? Mac and Windows builds don't use it, and it only
> >> applies to Linux.
> >>
> >> I haven't investigated the code much to see how the gstreamer libraries
> >> are used. The Linux distros now mostly use Freedesktop lower level
> >> interfaces except I don't know what Unity uses. Is building with
> >> gstreamer still needed/compliant with this? In short, how are video
> >> applications determined in Linux now? Do we need a different approach
> >> for integration of video objects in Linux?
> >>
> >> If anyone knows the history of this, it would be very helpful to this
> >> discussion.
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
>
> --
> --
> MzK
>
> "Less is MORE."
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: gstreamer status for 4.2.0-dev?

[Peter Kovacs]

The implementation can be found at avmedia/source/

I think we use native API / libs for Windows and Mac.


Am 28. Mai 2018 19:18:34 MESZ schrieb Kay Schenk :
>On 05/28/2018 12:05 AM, Peter kovacs wrote:
>> Imho the gstreamer libs are still the method of choice for doing
>multimedia.
>
>This is ONLY for Linux. So, how is multimedia "integrated" in AOO for
>Mac and Windows? Can someone point us to the applicable code areas for
>this?
>
>I have a feeling gstreamer was integrated long ago when no other
>multi-media standard/app for Linux existed. Now it seems VLC seems to
>the standard for the most part. (This is a dated web page but I think
>it's still a good reference:
>http://www.yolinux.com/TUTORIALS/LinuxTutorialMimeTypesAndApplications.html). 
>Basically, we are supplying gstreamer as a multimedia app to Linux when
>maybe this isn't really needed.
>
>>
>> The current state is that trunk can utilize the gstreamer API 1.0.0
>>
>> We have the issue not resolved the issue to provide gstreamer for
>different Distributions. (Main issue: centos6 is to old to support the
>new gstreamer 1.0.0 API)
>> We have 2 suggestions to solve the issue:
>> 1) implement 0.1.0 and 1.0.0 API. 
>> 2) move the implementation into an optional extention.
>>
>> Both solutions have currently not followed up. 
>>
>> All the best
>> Peter
>>
>> Am 26. Mai 2018 18:53:46 MESZ schrieb Kay Schenk
>:
>>> On 05/23/2018 05:35 AM, Jim Jagielski wrote:
 Subj line sez it all... where are we? There was a proposal to make
>it
>>> a run-time dependency but afaict there hasn't been any effort yet it
>>> doing that.
 I know we have a handful of other things TODO re: 4.2.0 but this
>>> seems to be an inflection point for the Linux builds and so I really
>>> think we need to resolve this if we have any intent in getting a
>4.2.0
>>> beta out in a reasonable time frame.
>>>
>>> What would happen if we simply stopped including the
>--with-gstreamer
>>> option in the build? Mac and Windows builds don't use it, and it
>only
>>> applies to Linux. 
>>>
>>> I haven't investigated the code much to see how the gstreamer
>libraries
>>> are used. The Linux distros now mostly use Freedesktop lower level
>>> interfaces except I don't know what Unity uses. Is building with
>>> gstreamer still needed/compliant with this? In short, how are video
>>> applications determined in Linux now? Do we need a different
>approach
>>> for integration of video objects in Linux?
>>>
>>> If anyone knows the history of this, it would be very helpful to
>this
>>> discussion.
>> -
>> 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

Re: gstreamer status for 4.2.0-dev?

[Kay Schenk]

On 05/28/2018 12:05 AM, Peter kovacs wrote:
> Imho the gstreamer libs are still the method of choice for doing multimedia.

This is ONLY for Linux. So, how is multimedia "integrated" in AOO for
Mac and Windows? Can someone point us to the applicable code areas for this?

I have a feeling gstreamer was integrated long ago when no other
multi-media standard/app for Linux existed. Now it seems VLC seems to
the standard for the most part. (This is a dated web page but I think
it's still a good reference:
http://www.yolinux.com/TUTORIALS/LinuxTutorialMimeTypesAndApplications.html). 
Basically, we are supplying gstreamer as a multimedia app to Linux when
maybe this isn't really needed.

>
> The current state is that trunk can utilize the gstreamer API 1.0.0
>
> We have the issue not resolved the issue to provide gstreamer for different 
> Distributions. (Main issue: centos6 is to old to support the new gstreamer 
> 1.0.0 API)
> We have 2 suggestions to solve the issue:
> 1) implement 0.1.0 and 1.0.0 API. 
> 2) move the implementation into an optional extention.
>
> Both solutions have currently not followed up. 
>
> All the best
> Peter
>
> Am 26. Mai 2018 18:53:46 MESZ schrieb Kay Schenk :
>> On 05/23/2018 05:35 AM, Jim Jagielski wrote:
>>> Subj line sez it all... where are we? There was a proposal to make it
>> a run-time dependency but afaict there hasn't been any effort yet it
>> doing that.
>>> I know we have a handful of other things TODO re: 4.2.0 but this
>> seems to be an inflection point for the Linux builds and so I really
>> think we need to resolve this if we have any intent in getting a 4.2.0
>> beta out in a reasonable time frame.
>>
>> What would happen if we simply stopped including the --with-gstreamer
>> option in the build? Mac and Windows builds don't use it, and it only
>> applies to Linux. 
>>
>> I haven't investigated the code much to see how the gstreamer libraries
>> are used. The Linux distros now mostly use Freedesktop lower level
>> interfaces except I don't know what Unity uses. Is building with
>> gstreamer still needed/compliant with this? In short, how are video
>> applications determined in Linux now? Do we need a different approach
>> for integration of video objects in Linux?
>>
>> If anyone knows the history of this, it would be very helpful to this
>> discussion.
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

-- 
--
MzK

"Less is MORE."


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Damjan Jovanovic]

3. Build on a newer CentOS or other distro.
4. Link to 1.0.0 using run-time dynamic linking, using that patch I made,
and only require the gstreamer-1.0.0 tarball at compile time to find the
headers.

Damjan

On Mon, May 28, 2018 at 9:06 AM Peter kovacs  wrote:

> Imho the gstreamer libs are still the method of choice for doing
> multimedia.
>
> The current state is that trunk can utilize the gstreamer API 1.0.0
>
> We have the issue not resolved the issue to provide gstreamer for
> different Distributions. (Main issue: centos6 is to old to support the new
> gstreamer 1.0.0 API)
> We have 2 suggestions to solve the issue:
> 1) implement 0.1.0 and 1.0.0 API.
> 2) move the implementation into an optional extention.
>
> Both solutions have currently not followed up.
>
> All the best
> Peter
>
> Am 26. Mai 2018 18:53:46 MESZ schrieb Kay Schenk :
> >On 05/23/2018 05:35 AM, Jim Jagielski wrote:
> >> Subj line sez it all... where are we? There was a proposal to make it
> >a run-time dependency but afaict there hasn't been any effort yet it
> >doing that.
> >>
> >> I know we have a handful of other things TODO re: 4.2.0 but this
> >seems to be an inflection point for the Linux builds and so I really
> >think we need to resolve this if we have any intent in getting a 4.2.0
> >beta out in a reasonable time frame.
> >
> >What would happen if we simply stopped including the --with-gstreamer
> >option in the build? Mac and Windows builds don't use it, and it only
> >applies to Linux.
> >
> >I haven't investigated the code much to see how the gstreamer libraries
> >are used. The Linux distros now mostly use Freedesktop lower level
> >interfaces except I don't know what Unity uses. Is building with
> >gstreamer still needed/compliant with this? In short, how are video
> >applications determined in Linux now? Do we need a different approach
> >for integration of video objects in Linux?
> >
> >If anyone knows the history of this, it would be very helpful to this
> >discussion.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: gstreamer status for 4.2.0-dev?

[Peter kovacs]

Imho the gstreamer libs are still the method of choice for doing multimedia.

The current state is that trunk can utilize the gstreamer API 1.0.0

We have the issue not resolved the issue to provide gstreamer for different 
Distributions. (Main issue: centos6 is to old to support the new gstreamer 
1.0.0 API)
We have 2 suggestions to solve the issue:
1) implement 0.1.0 and 1.0.0 API. 
2) move the implementation into an optional extention.

Both solutions have currently not followed up. 

All the best
Peter

Am 26. Mai 2018 18:53:46 MESZ schrieb Kay Schenk :
>On 05/23/2018 05:35 AM, Jim Jagielski wrote:
>> Subj line sez it all... where are we? There was a proposal to make it
>a run-time dependency but afaict there hasn't been any effort yet it
>doing that.
>>
>> I know we have a handful of other things TODO re: 4.2.0 but this
>seems to be an inflection point for the Linux builds and so I really
>think we need to resolve this if we have any intent in getting a 4.2.0
>beta out in a reasonable time frame.
>
>What would happen if we simply stopped including the --with-gstreamer
>option in the build? Mac and Windows builds don't use it, and it only
>applies to Linux. 
>
>I haven't investigated the code much to see how the gstreamer libraries
>are used. The Linux distros now mostly use Freedesktop lower level
>interfaces except I don't know what Unity uses. Is building with
>gstreamer still needed/compliant with this? In short, how are video
>applications determined in Linux now? Do we need a different approach
>for integration of video objects in Linux?
>
>If anyone knows the history of this, it would be very helpful to this
>discussion.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Kay Schenk]

On 05/23/2018 05:35 AM, Jim Jagielski wrote:
> Subj line sez it all... where are we? There was a proposal to make it a 
> run-time dependency but afaict there hasn't been any effort yet it doing that.
>
> I know we have a handful of other things TODO re: 4.2.0 but this seems to be 
> an inflection point for the Linux builds and so I really think we need to 
> resolve this if we have any intent in getting a 4.2.0 beta out in a 
> reasonable time frame.

What would happen if we simply stopped including the --with-gstreamer
option in the build? Mac and Windows builds don't use it, and it only
applies to Linux. 

I haven't investigated the code much to see how the gstreamer libraries
are used. The Linux distros now mostly use Freedesktop lower level
interfaces except I don't know what Unity uses. Is building with
gstreamer still needed/compliant with this? In short, how are video
applications determined in Linux now? Do we need a different approach
for integration of video objects in Linux?

If anyone knows the history of this, it would be very helpful to this
discussion.

-- 

--
MzK

"Less is MORE."


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: gstreamer status for 4.2.0-dev?

[Jose R R]

Hopefully I will not intrude, but...

On Wed, May 23, 2018 at 5:35 AM, Jim Jagielski  wrote:
>
> Subj line sez it all... where are we? There was a proposal to make it a 
> run-time dependency but afaict there hasn't been any effort yet it doing that.

On May 19-20, 2018, I pulled 4.2.0-1 trunk 1831928 and built
OpenOffice with my local build of GCC-5 GNU compiler.
I simply apt- and got
https://packages.debian.org/stretch/libgstreamer1.0-dev from Debian
9.x repository for AMD64.

>
> I know we have a handful of other things TODO re: 4.2.0 but this seems to be 
> an inflection point for the Linux builds and so I really think we need to 
> resolve this if we have any >intent in getting a 4.2.0 beta out in a 
> reasonable time frame.

In my build I experienced no issues opening previous ODT entities nor
creating new ones. On the other hand, after testing a multimedia .mp4
clip (which plays excellently) if I click, i.e., select, an empty area
ApacheOO simply crashes. Here is a small screen recording of the
issue.

< https://metztli.it/blog/index.php/ixiptli/ >


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Metztli Reiser4: Debian Stretch w/ Linux 4.15 AMD64
-
feats ZSTD compression https://sf.net/projects/metztli-reiser4/
---
Official current Reiser4 resources: https://reiser4.wiki.kernel.org/

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

gstreamer status for 4.2.0-dev?

[Jim Jagielski]

Subj line sez it all... where are we? There was a proposal to make it a 
run-time dependency but afaict there hasn't been any effort yet it doing that.

I know we have a handful of other things TODO re: 4.2.0 but this seems to be an 
inflection point for the Linux builds and so I really think we need to resolve 
this if we have any intent in getting a 4.2.0 beta out in a reasonable time 
frame.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org