On Thu, 5 Jan 2017 22:36:52 +0000 Peter Flynn <[email protected]> said:
> On 11/02/2016 10:01 PM, Peter Flynn wrote: > > I *know* you're really good...I was letting prior experience cloud my > > vision. I'm away this weekend but I'll give it a try later. > > Hah. It worked. Interesting. > > The page at https://www.enlightenment.org/distros/debian-start is they key. > > 1. Apparently libpng12-dev *does* get installed on some platforms still > when you install xubuntu-16.04, but NOT if you install 16.04_01. > > 2. libxp-dev is dead, and has been replaced by x11proto-print-dev, so > editing that into the list of packages works fine. package names and such change over time for distros... this is why it's a wiki so as pellpe find that things changed a bit... they can alter it. :) to some extent people have to be self-starters in a little missing thnig like this they can easily track down the changes that happen in debian, ubuntu, arch etc. - kind of like a team effort. :) > The rest of the script ran as writ, barring a few little bobbles where > the compiler warned about misdeclared variables, which is only to be > expected in large and complex systems. Nothing that looked serious. actually it seems debian gcc's by default turn on more warnings that vanilla gcc (eg what arch uses). with a vanilla gcc efl is warning-free atm (even with a bunch of extra warnings turned on like -Wno-unused-but-set-parameter -Wno-clobbered -W -Wall -Wextra which is what i use). i haven't sat down and looked into the debian warnings as they are on only my arm systems and so slower builds and i dont spend all day beating on them... :) > Right at the end, I did another update/upgrade for an unrelated reason, > and it kicked up x11proto-print-dev saying it was unused and could be > removed with apt autoremove :-) So it's basically a catalyst, which I > think is largely what Carsten was alluding to. well the package system didn't know a COMPILED piece of sw used it (efl) because its not in a package... > So now I have a nicely running E on virgin stock Xubuntu 16.04. Thank > you all very much for your patience and skill. > > NOW...I already have e17 from the Ubuntu repos running on all my other > 16.04 systems. What's the best path to enligh^H^H^H^H^H^Hreplacement? > > a. remove and purge enlightenment and build from scratch on each system > > b. remove and purge enlightenment on each system, and try to work out > what files from my newly-working test system need to be copied across as long as all your system sport the same packages and dependencies you should be able to easily just tar up /usr/local or whatever prefix you put e and efl in and untar on the other systems.. you should indeed wipe the existing efl and e packages from the systems to avoid conflicts (can be handled if you know what you are doing without removing the pkgs... but i just suggest removal as it's simpler) > c. go the whole hog and try to package it up for the distro (I don't > think I have the skill or the time to do this and support it). > > ///Peter > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
