On Tue, 31 Jan 2017 13:07:50 +0100 ani...@astier.eu said: so what i see is just an "executable" "debian install docs" or "ubuntu install docs" or "fedora" etc. ... but what about:
arch gentoo slackware opensbd freebsd suse rhel mint nixos gobolinux ... you get the idea - it becomes an endless list of packages for an endless list of distributions and variants... (also ubuntu for example needs to be split between 14.x, 15.x 16.x etc. as the package deps change)... its a horrible intractable problem with so many permutations that it just is insane... which is why a lot of it is left "fuzzy" and up to people to figure out with per distro guides being generally fairly rough... :) there is really only one solution i can think of that works: ship dependencies beyond an incredibly small core (eg depend on libc/libm and friends and nothing else). that means instead having a builder that would fetch all the efl's dependencies and build them and install then also build and install efl too. e.g. in /opt/e - and then you can just ship a tarball of /opt/e and avoid everything else. this is a solution that actually might work as it totally side-steps the "million distros and versions and permutations of them" problem. > Over the years, the dependency list for EFL has grown quite a bit. As a > results, it's often been a pain to build the whole thing from git as a > new developer (if you don't want to use your distro packages). > You have to figure out what to install, by finding which package > correspond to the libs described in the Requirements section of the > README[1]. Or to apt-get build-dep old dependencies based on the current > package. Or, you can try to follow the outdated docs on the wiki[2] > for your distro. > > I have tried updating those docs once[3] using a bare distro, in order > to make sure we have the full list of needed dependencies. > > What would be better would be to make sure the process I used to verify > the dependency list is reproductible, so that we could simply document > the dependencies for each distro. That's where distro-builder comes in: > https://github.com/anisse/distro-builder > > It's a relatively simple script that currently builds efl and > terminology on fedora 24/25, debian stretch and ubuntu 16.04/16.10. > > The final goal would be to have this script and the dependency files in > the efl tree, and running it regularly, possibly on CI. > > It could even help making sure the current cmake transition goes > smoothly on different distros :-) > > I'm looking forward to your feedback. > > Anisse > > [1] https://git.enlightenment.org/core/efl.git/tree/README?h=v1.18.4#n444 > [2] https://www.enlightenment.org/docs > [3] > https://git.enlightenment.org/website/www-content.git/commit/pages/distros/fedora-start.txt?id=a640068093a40797386716d500484ffc2b325fec > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > 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" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
