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