gstreamer status for 4.2.0-dev?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
30 messages Options
12
Reply | Threaded
Open this post in threaded view
|

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 <[hidden email]> 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 <[hidden email]>
>>> wrote:
>>>>
>>>>
>>>>
>>>> 29.05.2018, 21:30, "Jim Jagielski" <[hidden email]>:
>>>>> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: gstreamer status for 4.2.0-dev?

Peter Kovacs-2
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 <[hidden email]>:

>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 <[hidden email]>
>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
><[hidden email]>
>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> 29.05.2018, 21:30, "Jim Jagielski" <[hidden email]>:
>>>>>> 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: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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 <[hidden email]>:
>> 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 <[hidden email]>
>> 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
>> <[hidden email]>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> 29.05.2018, 21:30, "Jim Jagielski" <[hidden email]>:
>>>>>>> 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: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: gstreamer status for 4.2.0-dev?

Peter Kovacs-3
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 <[hidden email]>:

>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
><[hidden email]>:
>>> 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 <[hidden email]>
>>> 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
>>> <[hidden email]>
>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>> 29.05.2018, 21:30, "Jim Jagielski" <[hidden email]>:
>>>>>>>> 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: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: gstreamer status for 4.2.0-dev?

Jim Jagielski
In reply to this post by Kay Schenk-2


> On Jun 4, 2018, at 6:15 PM, Kay Schenk <[hidden email]> 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 ;)

Reply | Threaded
Open this post in threaded view
|

Re: gstreamer status for 4.2.0-dev?

Jim Jagielski
In reply to this post by Marcus (OOo)
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 <[hidden email]> wrote:
>
> Am 05.06.2018 um 00:15 schrieb Kay Schenk:
>> On Mon, Jun 4, 2018 at 12:09 PM, Jim Jagielski <[hidden email]> 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 <[hidden email]>
>>> wrote:
>>>>
>>>>
>>>>
>>>> 29.05.2018, 21:30, "Jim Jagielski" <[hidden email]>:
>>>>> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: gstreamer status for 4.2.0-dev?

Marcus (OOo)
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 <[hidden email]> wrote:
>>
>> Am 05.06.2018 um 00:15 schrieb Kay Schenk:
>>> On Mon, Jun 4, 2018 at 12:09 PM, Jim Jagielski <[hidden email]> 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 <[hidden email]>
>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> 29.05.2018, 21:30, "Jim Jagielski" <[hidden email]>:
>>>>>> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: gstreamer status for 4.2.0-dev?

Jim Jagielski


> On Jun 6, 2018, at 3:21 PM, Marcus <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: gstreamer status for 4.2.0-dev?

Marcus (OOo)
Am 06.06.2018 um 21:37 schrieb Jim Jagielski:

>
>
>> On Jun 6, 2018, at 3:21 PM, Marcus <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: gstreamer status for 4.2.0-dev?

Peter Kovacs-3
In reply to this post by Jim Jagielski
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 <[hidden email]>:

>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 <[hidden email]> wrote:
>>
>> Am 05.06.2018 um 00:15 schrieb Kay Schenk:
>>> On Mon, Jun 4, 2018 at 12:09 PM, Jim Jagielski <[hidden email]>
>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
><[hidden email]>
>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> 29.05.2018, 21:30, "Jim Jagielski" <[hidden email]>:
>>>>>> 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: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

12