Re: Statically linked build of 0install

Thomas Leonard <[email protected]> Sat, 17 Nov 2018 15:39:41 +0000
Newsgroups gmane.comp.file-systems.zero-install.devel
Message-ID <CAG4opy_414ns+MxohY=TFf6CbPX0U3xs1zFUX+_OKkOFJpGy7Q@mail.gmail.com>
In Tue, 30 Oct 2018 at 21:14, Thomas Leonard <[email protected]> wrote:
>
> On Sun, 28 Oct 2018 at 13:28, Bastian Eicher <[email protected]> wrote:
> >
> > Hi all,
> >
> > I've recently been experimenting with running 0install in Docker containers
> > based on various Linux distributions. Since I wanted to use the latest
> > version I downloaded the pre-built binaries listed here:
> > http://0install.net/tools/0install.xml
> >
> > On Debian Stable and Ubuntu 18.04 I simply had to run "apt-get install
> > libcurl3", download and extract the 0install archive and was good to go.
> > However, on Debian Testing and Ubuntu 18.10 libcurl3 has been replaced with
> > libcurl4. After installing this 0install fails to launch with:
> > "/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found"
> > Installing a libcurl3 package intended for an older distro also isn't a good
> > option, since libcurl3 and libcurl4 both attempt to install the same file
> > and therefore cannot co-exist on the same system. Forcibly downgrading
> > libcurl also breaks the curl command on the system.
> > Running the binaries on Alpine is of course even trickier, since that distro
> > does not use glibc.
> >
> > This got me thinking: Would it be practical to create completely statically
> > linked builds of 0install? A quick Google search turned up a blog article
> > titled "Creating Static Linux Binaries in OCaml"
> > (http://rgrinberg.com/posts/static-binaries-tutorial/). Since I have no
> > experience with OCaml yet, I'm not sure if this is applicable to 0install.
> > @Thomas: Could you perhaps take a quick look?
>
> Static linking libcurl itself probably isn't difficult (or we could
> replace it with cohttp if we dropped FTP support; I guess no-one is
> using FTP now anyway).

I checked the mirror for public feeds referencing FTP sites.
These FTP sites are still running and being used as the main download
URL by their projects:

ftp://xmlsoft.org
ftp://ftp.alsa-project.org

These FTP sites are used in some feeds, but there is an HTTP alternative:

ftp://ftp.gnu.org
ftp://ftp.gmplib.org
ftp://ftp.lyx.org
ftp://ftp.gnome.org
ftp://ftp.vim.org
ftp://ftp.osuosl.org

We should probably start logging warnings about FTP sites. We could
also drop support in the 0install client, and just copy the archives
to the mirror service to avoid breaking anything.
Or just drop it anyway - no feed using FTP has been updated since Jan 2017.


-- 
talex5 (GitHub/Twitter)        http://roscidus.com/blog/
GPG: 5DD5 8D70 899C 454A 966D  6A51 7513 3C8F 94F6 E0CC