Re: [Nix-dev] Better support for channels in nixos

[Tomasz Czyż]

2016-09-01 20:23 GMT+01:00 Matthew O'Gorman :

> Domen Kožar  writes:
>
> > We can (and do) backport new services to stable releases.
>
>   Not trying to argue, but the example I gave still stands? The service
>   was not back ported.
> >
> > For "Another example would be I am developing a service that I want to
> test
> > on my system" I don't really understand what you're trying to say.
> >
>   The other example, say I ported an application to nixos, like huginn,
>   and I want to test it on my system easily.
>
you can do this with nix-build, you don't need all channel to install one
package.

>
>   A third example would be a package that moves ridiculously quickly,
>   like gitlab, stable is on 8.5, unstable is on 8.10, the current
>   release is 8.11.

 You can create your package set on top of nixpkgs and you can upgrade
versions by yourself and still have all the packages from the original
nixpkgs, no problem with that.

my-packages = (import  {}) // {upgraded-gitlab = mkDerivation
..}

or probably better to use packageOverrides

>


>   I think it would be easier to maintain a system if I could have point
>   to multiple places for channels, and then in the install specifically
>   describe which provider I want to use.
>
if I understand this correctly, whole point of nix is to reduce source and
have as few source of truth as possible (IMHO).

>
> --
> Matthew O'Gorman
> BM-NBUmia4p88Jny5bZbRGcMt64SWWp5WVv
> TorChat: 5w3dtk7nhkkijcpc
> Site: https://b.rldn.net
> Xim/Email: m...@rldn.net
> mog@rldn:~$ fortune wisdom -s|cowsay -f /dev/null
>  ___
> < Life exists for no known purpose. >
>  ---
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>


-- 
Tomasz Czyż
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Better support for channels in nixos

[Matthew O'Gorman]

Domen Kožar  writes:

> We can (and do) backport new services to stable releases.

  Not trying to argue, but the example I gave still stands? The service
  was not back ported.
>
> For "Another example would be I am developing a service that I want to test
> on my system" I don't really understand what you're trying to say.
>
  The other example, say I ported an application to nixos, like huginn,
  and I want to test it on my system easily.

  A third example would be a package that moves ridiculously quickly,
  like gitlab, stable is on 8.5, unstable is on 8.10, the current
  release is 8.11.

  I think it would be easier to maintain a system if I could have point
  to multiple places for channels, and then in the install specifically
  describe which provider I want to use.
  
-- 
Matthew O'Gorman
BM-NBUmia4p88Jny5bZbRGcMt64SWWp5WVv
TorChat: 5w3dtk7nhkkijcpc
Site: https://b.rldn.net
Xim/Email: m...@rldn.net
mog@rldn:~$ fortune wisdom -s|cowsay -f /dev/null
 ___ 
< Life exists for no known purpose. >
 --- 


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Better support for channels in nixos

[Domen Kožar]

We can (and do) backport new services to stable releases.

For "Another example would be I am developing a service that I want to test
on my system" I don't really understand what you're trying to say.

On Thu, Sep 1, 2016 at 8:33 PM, Matthew O'Gorman  wrote:

> I don't know if I am going to use the right vocabulary, but as we get
> closer to the next release I thought I would bring up my need for
> supporting multiple channels at the nixos level.
>
> For example, currently in unstable there is a package for mosquitto
> service, where as the current release only has the actual application.
> Another example would be I am developing a service that I want to test
> on my system.  One way to fix both of these problems is to just point my
> system at the unstable channel, but given my system is used for more
> things that is not preferable, another option could be allowing
> containers to specify a channel and then I could run each of these
> projects in their own nixos container. Given that we are about to lock
> down for another 6 months I was hoping we could address this.
>
> If I am mistaken about this please correct me.
>
> thanks
>
> --
> Matthew O'Gorman
> BM-NBUmia4p88Jny5bZbRGcMt64SWWp5WVv
> TorChat: 5w3dtk7nhkkijcpc
> Site: https://b.rldn.net
> Xim/Email: m...@rldn.net
> mog@rldn:~$ fortune wisdom -s|cowsay -f /dev/null
>  _
> / Life is the living you do, Death is the \
> | living you don't do.|
> | |
> \ -- Joseph Pintauro  /
>  -
>
> ___
> 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

[Nix-dev] Better support for channels in nixos

[Matthew O'Gorman]

I don't know if I am going to use the right vocabulary, but as we get
closer to the next release I thought I would bring up my need for
supporting multiple channels at the nixos level.

For example, currently in unstable there is a package for mosquitto
service, where as the current release only has the actual application.
Another example would be I am developing a service that I want to test
on my system.  One way to fix both of these problems is to just point my
system at the unstable channel, but given my system is used for more
things that is not preferable, another option could be allowing
containers to specify a channel and then I could run each of these
projects in their own nixos container. Given that we are about to lock
down for another 6 months I was hoping we could address this.

If I am mistaken about this please correct me.

thanks

-- 
Matthew O'Gorman
BM-NBUmia4p88Jny5bZbRGcMt64SWWp5WVv
TorChat: 5w3dtk7nhkkijcpc
Site: https://b.rldn.net
Xim/Email: m...@rldn.net
mog@rldn:~$ fortune wisdom -s|cowsay -f /dev/null
 _ 
/ Life is the living you do, Death is the \
| living you don't do.|
| |
\ -- Joseph Pintauro  /
 - 


signature.asc
Description: PGP signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev