Date: Sun, 22 May 2016 18:49:44 +0200 From: Kurt Jaeger <lists@opsec.eu> To: Matthias Apitz <guru@unixarea.de>, freebsd-ports@freebsd.org Subject: Re: myrepo.conf && url: file:.... Message-ID: <20160522164944.GH41922@home.opsec.eu> In-Reply-To: <20160522163914.GA6150@c720-r292778-amd64> References: <20160522124450.GA4150@c720-r292778-amd64> <DUB125-W9370671AFE6EBC905ADD0ECD4D0@phx.gbl> <20160522163914.GA6150@c720-r292778-amd64>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > > the FILE-protocol specification allows for a hostname, so in general it is: > > file://<host>/<path> > > When specifying a path on the local machine, the <host>-part > > can be left out (or replaced with localhost), leaving you with > > either > > file://localhost/<path> > > or its abbreviation > > file:///<path>. > Thanks for the feedback. I think, the man page pkg.conf(5) should > mention this, esp. when the old systax does not work anymore. pkg.conf(5) refers to libfetch(3) [this should be fetch(3)], which explains the syntax, which correctly mentions file:///, but in a very unreadable way: <scheme>:(//(<user>(:<pwd>)?@)?<host>(:<port>)?)?/(<document>)? But: This allows file:/path, which your tests show to fail. Interesting. -- pi@opsec.eu +49 171 3101372 4 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160522164944.GH41922>