'Re: [Nix-dev] Two declarative ways to install a package?'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nix-dev
Subject:    Re: [Nix-dev] Two declarative ways to install a package?
From:       "Guillaume Maudoux (Layus)" <layus.on () gmail ! com>
Date:       2016-08-12 14:15:46
Message-ID: 145356dc-1c2b-4088-1030-7118d2792ec1 () gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

I would rather see it as a convenience.
The package is in your store anyway, so better make it available in user
shells.

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.

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 ?

Le 12/08/16 à 15:44, Moritz Ulrich a écrit :
> If the service doesn't provide any necessary command line tools that
> would justify putting it into the global environment, I would say it's a
> bug, yes.
>
>
> Anders Lundstedt <anders@anderslundstedt.se> writes:
>
>> On Thu, Aug 11, 2016 at 9:35 PM, Kevin Cox <kevincox@kevincox.ca> wrote:
>>> It's also important to not that services generally (never?) actually
>>> "install" the package.
>> I did a quick check among my enabled services. Two services that add
>> their packages to environment.systemPackages are the transmission and
>> shairport-sync services. The shairport-sync.nix service file provides
>> no motivation for this. Should this be considered a bug?
>> _______________________________________________
>> nix-dev mailing list
>> nix-dev@lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
> _______________________________________________
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Attachment #5 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>I would rather see it as a convenience.<br>
      The package is in your store anyway, so better make it available
      in user shells.<br>
    </p>
    <p>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.<br>
      Forcing users to install it in their own environments could even
      lead to version mismatches.</p>
    <p>If exposing a package from its service happens to be annoying
      (for whatever reason),<br>
      may I suggest suggest to pull-request an opt-out option for it ?</p>
    <br>
    <div class="moz-cite-prefix">Le 12/08/16 à 15:44, Moritz Ulrich a
      écrit :<br>
    </div>
    <blockquote cite="mid:87fuqa5cgv.fsf@tarn-vedra.de" type="cite">
      <pre wrap="">
If the service doesn't provide any necessary command line tools that
would justify putting it into the global environment, I would say it's a
bug, yes.

Anders Lundstedt <a class="moz-txt-link-rfc2396E" \
href="mailto:anders@anderslundstedt.se">&lt;anders@anderslundstedt.se&gt;</a> writes:

</pre>
      <blockquote type="cite">
        <pre wrap="">On Thu, Aug 11, 2016 at 9:35 PM, Kevin Cox <a \
class="moz-txt-link-rfc2396E" \
href="mailto:kevincox@kevincox.ca">&lt;kevincox@kevincox.ca&gt;</a> wrote: </pre>
        <blockquote type="cite">
          <pre wrap="">It's also important to not that services generally (never?) \
actually "install" the package.
</pre>
        </blockquote>
        <pre wrap="">
I did a quick check among my enabled services. Two services that add
their packages to environment.systemPackages are the transmission and
shairport-sync services. The shairport-sync.nix service file provides
no motivation for this. Should this be considered a bug?
_______________________________________________
nix-dev mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:nix-dev@lists.science.uu.nl">nix-dev@lists.science.uu.nl</a> <a \
class="moz-txt-link-freetext" \
href="http://lists.science.uu.nl/mailman/listinfo/nix-dev">http://lists.science.uu.nl/mailman/listinfo/nix-dev</a>
 </pre>
      </blockquote>
      <pre wrap="">
</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
nix-dev mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:nix-dev@lists.science.uu.nl">nix-dev@lists.science.uu.nl</a> <a \
class="moz-txt-link-freetext" \
href="http://lists.science.uu.nl/mailman/listinfo/nix-dev">http://lists.science.uu.nl/mailman/listinfo/nix-dev</a>
 </pre>
    </blockquote>
    <br>
  </body>
</html>

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

[prev in list] [next in list] [prev in thread] [next in thread] 