On Thu, 2 May 2019 08:52:01 +0000 Jonathan Aquilina <jaquil...@eagleeyet.net>
said:

> For EFL cant we do like other projects do such as libreoffice set a minimum
> base line version or newer for meason?

that's EXACTLY what we do - and its too new for suse in this case as simon
describes. this will get fixed eventually with newer suse's though so i'm a bit
less worried about this and see it as a hiccup rather than a big issue. :)

> Regards,
> Jonathan
> 
> Regards,
> Jonathan Aquilina
> Owner EagleEyeT
> 
> ________________________________
> From: Simon Lees <sfl...@suse.de>
> Sent: Thursday, May 2, 2019 10:46 AM
> To: enlightenment-devel@lists.sourceforge.net
> Subject: Re: [E-devel] EFL Autotools freeze proposal
> 
> Generally stable releases will get version updates for point releases,
> and if there are any other major bugs that are fixed after i'll normally
> backport them, if thats too hard I may consider a major version update.
> 
> We tend to encourage people who want the latest everything to use the
> rolling release instead, or wait for the next leap point release which
> will be within a year. There are repo's that get used for development
> where people could get a newer version but we generally don't encourage
> it, and they would still require a new enough meson to be in the core
> system in order to build. Because enabling a newer version of E
> shouldn't force you onto a non system build of Meson thats not being as
> well maintained.
> 
> For the crazy adventurous there are repo's that even have git builds,
> but generally normal openSUSE users shouldn't need to add any additional
> repos to there system bar 1 or 2 where legal issues get in the way,
> unlike ubuntu where not everything makes it into the core distro in
> openSUSE we encourage everything possible to be in the main distro at an
> appropriate version depending on whether users are expecting a "stable
> system that changes less" or a "rolling release". So the problem we hit
> and are discussing is that the appropriate version of meson in the next
> point release of openSUSE is too old to build the ideal version of efl,
> which will likely end up blocking a new version of e (which does work
> with that version of meson). Extra repo's are not a solution for 99% of
> users who will just use the version that ships in the distro, which in
> fairness may not be that big an issue because it is rather stable and
> works really well on X11, but there is the potential that they will
> still be using that version in 2-3 years unless we lower the version of
> meson required by efl slightly.
> 
> On 02/05/2019 14:08, Jonathan Aquilina wrote:
> > Hi Simon,
> >
> > What happens in terms of OpenSuse in the sense of giving those on stable
> > versions of Suse the latest versions of e? Won’t a 3rd party repo still be
> > needed until the next release is released with a newer version of e?
> >
> > Regards,
> > Jonathan
> >
> > Regards,
> > Jonathan Aquilina
> > Owner EagleEyeT
> >
> > ________________________________
> > From: Simon Lees <sfl...@suse.de>
> > Sent: Thursday, May 2, 2019 1:12 AM
> > To: enlightenment-devel@lists.sourceforge.net
> > Subject: Re: [E-devel] EFL Autotools freeze proposal
> >
> > I have ways of creating 3rd party repo's easily, but currently you can
> > install enlightenment from the openSUSE installer, and I'd like to keep
> > that at the latest version for each new version of leap, so i'd like e23
> > or later in Leap 15.2 (about a year away), which will probably need a
> > reasonably new efl, but will likely only have meson 0.46.0 which is fine
> > for e but atm not for efl.
> >
> > There are alot of people using e from the installer, I keep bumping into
> > them at conferences etc, GNU Health have been using openSUSE +
> > enlightenment on all there raspberry pi's etc, so there is a significant
> > number of people using e in this way, and i'd like them to stay
> > reasonably up to date.
> >
> > On 01/05/2019 16:12, Jonathan Aquilina wrote:
> >> Hi Simon,
> >>
> >> Open suse is an rpm based distro correct?
> >>
> >> If yes why not creat a copr repo that will contain the newer stuff?
> >>
> >> Get Outlook for iOS<https://aka.ms/o0ukef>
> >>
> >> ________________________________
> >> From: Simon Lees <sfl...@suse.de>
> >> Sent: Wednesday, May 1, 2019 02:13
> >> To: Carsten Haitzler (The Rasterman); Enlightenment developer list
> >> Subject: Re: [E-devel] EFL Autotools freeze proposal
> >>
> >>
> >>
> >> On 30/04/2019 21:39, Carsten Haitzler (The Rasterman) wrote:
> >>> On Tue, 30 Apr 2019 18:30:20 +0930 Simon Lees <sfl...@suse.de> said:
> >>>
> >>>>
> >>>>
> >>>> On 30/04/2019 17:40, Carsten Haitzler (The Rasterman) wrote:
> >>>>> On Mon, 29 Apr 2019 15:20:19 -0700 Ross Vandegrift <r...@kallisti.us>
> >>>>> said:
> >>>>>
> >>>>>> On Mon, Apr 29, 2019 at 05:30:33AM +0000, Jonathan Aquilina wrote:
> >>>>>>> I think everyone is missing the point. What you are saying is true but
> >>>>>>> that is why then they say if you want newer stuff to use a PPA for it
> >>>>>>> even though its not in the main repo's
> >>>>>>
> >>>>>> Yes, anyone can make a PPA. But you're talking to the maintainers of
> >>>>>> distro packaging - we try to put packages into distros for real :)
> >>>>>
> >>>>> and i think this was covered - a stable distro release that will not
> >>>>> upgrade meson out of principle (that's the definition of stable) isn't
> >>>>> going to upgrade efl either for the same reasons... so i think the
> >>>>> topic is kind of moot. if someone wants to make pkgs for such distros
> >>>>> they can create upgraded meson packages too etc. if they want to go the
> >>>>> "all done by pkgs" path :)
> >>>>>
> >>>>
> >>>> This is kind of right, in an openSUSE context for a new service pack we
> >>>> probably won't update Meson because it effects alot but we can update
> >>>> efl / e because it doesn't affect as much, we could also add it if it
> >>>> didn't exist. Further if a new version of efl fixed a serious bug that
> >>>> was hard to backport we would also take the version update.
> >>>
> >>> tho meson doesn't affect THAT much... it's a build tool not a "runtime
> >>> tool". it isn't int he realms of libc, Xserver, bash etc.
> >>>
> >>
> >> Yeah there's a lot of stuff thats using meson to build now, and a meson
> >> update effects any updates we do for anything thats built with it due to
> >> needing full QA cycles to verify that the package was built correctly
> >> which is why enterprise distro's prefer not to update build tools mid
> >> cycle.
> >>
> >>
> >>>> In ubuntu's case from memory the service packs tend to only be a new
> >>>> installer containing all the updates so its probably less likely, but I
> >>>> don't remember how ubuntu works 100% so I could be wrong.
> >>>
> >>> in our case if a new efl needs a new meson, then... that's what it needs
> >>> and an efl upgrade is not likely to happen then from the core distro.
> >>> ppa's and equivalents can manage to fill that gap. this problem will go
> >>> away over time as meson matures etc. etc. so this is a short-term problem
> >>> as such. :)
> >>>
> >>
> >> Yep but in openSUSE's case that may mean keeping e22 through all the
> >> leap 15.X releases which I really don't want to do because I cant
> >> support it, so welcome back to the world of having bugs reported that
> >> are already fixed.
> >>
> >> --
> >>
> >> Simon Lees (Simotek) http://simotek.net
> >>
> >> Emergency Update Team keybase.io/simotek
> >> SUSE Linux Adelaide Australia, UTC+10:30
> >> GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
> >>
> >>
> >> _______________________________________________
> >> enlightenment-devel mailing list
> >> enlightenment-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> >>
> >> _______________________________________________
> >> enlightenment-devel mailing list
> >> enlightenment-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> >>
> >
> > --
> >
> > Simon Lees (Simotek) http://simotek.net
> >
> > Emergency Update Team keybase.io/simotek
> > SUSE Linux Adelaide Australia, UTC+10:30
> > GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
> >
> >
> > _______________________________________________
> > enlightenment-devel mailing list
> > enlightenment-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> >
> > _______________________________________________
> > enlightenment-devel mailing list
> > enlightenment-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> >
> 
> --
> 
> Simon Lees (Simotek) http://simotek.net
> 
> Emergency Update Team keybase.io/simotek
> SUSE Linux Adelaide Australia, UTC+10:30
> GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
> 
> 
> _______________________________________________
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> 
> _______________________________________________
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> 


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
Carsten Haitzler - ras...@rasterman.com



_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to