On Sat, 13 Jul 2019 09:31:21 +0200 Pierre Couderc <pie...@couderc.eu> said:
> > On 7/13/19 12:41 AM, Ross Vandegrift wrote: > > On Sat, Jul 13, 2019 at 12:30:05AM +0200, Pierre Couderc wrote: > >> I had tried using the buster .deb package but I renounce because of a bad > >> bughttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912356 which makes > >> using it impossible... > > Is this the right bug? #912356 affects terminology, not E. > > > > Are you trying to build against the Debian EFL packages or EFL that you > > built yourself? > > > > I am sorry to not be clear... > > As I am a basic user of e, I did hope to use the buster enlightenment > packages including "terminology/testing,now 1.3.2-1 amd64" and no more > build them myself. > > This is for me impossible as bug #912356 makes terminology impossible > to use. > > So I turn back to building it myself... And it is not easy ! Gladly > every time I fail, Raster comes at my help... (Thank you Raster !) > > I think it is a strategic question, do "you" want e to be used by > "normal" people ? If yes : > > 1- a correct release should be available at least in buster : a bug like > #912356 should be corrected in 3 days (including WE)... It should be > classified as "fatal" not "normal". complain to your debian packagers. debian is a "closed system" in that we (upstream) can't affect what debian packagers package, what options they enable or when they update. you have to become a debian developer (go through an approval process) and frankly... i don't use debian. i have enough to do and am not going to through all of that for something i don't even use. i DO maintain the arch AUR -git builds for a few e pkgs because i use arch on many systems (arm ones too). luckily these double as build instructions for any distro... :) > 2- for those who build from sources, the README, or INSTALL and the > wiki, should give a Howto build, supposing that the user knows nothing > of meson or git of python... I am ready to contribute in this sense. we moved a few weeks ago so it's new. enlightenment, terminology and rage all moved a long time ago and so have all of that in place. you are dealing with git master and it changes and it's not a "release" so documentation will lag - especially if it's "common stuff devs already know". the docs tend to get fixed up just prior to a release. :) > I like enlightenment, and more than that, I use it everyday ! and I > support all you developers. my suggestion would be to hassle the debian packagers to ensure they stay up to date, or offer to become the package maintainer. we can't go packaging it for all distributions. we're just not going to do that. there are 100's of them. :) > But I should not spend 1 day (after 50 years in computing) trying to > build it... Ok, I am a bit stupid... I do it, but it may explain that I > am maybe the only one user of Enlightenment... well the "look at the PKGBUILDS" was good advice... :) > _______________________________________________ > enlightenment-users mailing list > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
