--===============0949161672841587882==
Content-Type: multipart/signed; micalg=pgp-sha256;
 boundary="Sig_/nfDC/Quc8ewZ9F5VzHllO3k"; protocol="application/pgp-signature"

--Sig_/nfDC/Quc8ewZ9F5VzHllO3k
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Fri, 12 Aug 2016 16:15:46 +0200 "Guillaume Maudoux (Layus)"
<layus.on@gmail.com> wrote:
> I would rather see it as a convenience.
> The package is in your store anyway, so better make it available in
> user shells.

No, only expose what is needed or wanted explicit (explicit is better
then implicit;-)). Just because I want mpd to run on my machine,
doesn't mean I want every user to run its own mpd (and wonder why the
default-port is already in use). For example.

> With mysql for example, having the mysql command in your path is not
> strictly necessary, but it would be really annoying not to have it.
> Forcing users to install it in their own environments could even lead
> to version mismatches.

This largely depends on the package, doesn't it?

For the mysql-service to expose the mysql-commandline tool is a nice
convenience, at the same time exposing the mysqld binary is needless
and allows other apps to use that binary without actually depending on
it. It also allows foes to use it directly from your environment
without dealing specially with nix.

For the nginx-package to expose the nginx-daemon binary to your
environment isa bit useless for the same reasons explained with mysqld
exposed. But are there user-tools for nginx that should be exposed?

Maybe it would be better if there was a mysql and a mysql-server
package and the mysql-service would use the mysql-server itself and
expose the mysql commandline to the environment without exposing the
server binary?

> If exposing a package from its service happens to be annoying (for
> whatever reason),
> may I suggest suggest to pull-request an opt-out option for it ?

For security and sanity reason, it should be opt-in.

- Arnold

--Sig_/nfDC/Quc8ewZ9F5VzHllO3k
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iF4EAREIAAYFAlet8ywACgkQtuvagsE+DE7DPwEAuVUBvEwUANw2QaIWUCL+BwTf
d3JQgBukPMX0KxR/mV4BAOxUTDixNikCdrxB5+DwB03Fdmwi6rOpgc0DLjG5wCLN
=4Zzt
-----END PGP SIGNATURE-----

--Sig_/nfDC/Quc8ewZ9F5VzHllO3k--

--===============0949161672841587882==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

--===============0949161672841587882==--