I would say it depends on what are you planning to do with your packages. If you are planning to push them to upstream, that's the good way IMHO.
In the other case I would create custom packages in ~/.nixpkgs/config.nix (and friends) or custom channel so your packages could be developed "independently" from nixpkgs (of course you could still use/depend on nixpkgs) 2016-04-11 19:05 GMT+00:00 Vladimír Čunát <[email protected]>: > On 04/10/2016 08:51 PM, Anderson Torres wrote: > > My question is: how can I "update" Current if I update Nixos locally, > > AND propagate the update to the derived branches? > > You might use topgit workflow. It's quite a nice tool to develop > multiple features at once that can *depend* on each other. AFAIK it > assumes you want to export one commit per feature in the end, which > might not be what you want... > > (Underneath it uses merge commits, not rebasing.) > > --Vladimir > > > > _______________________________________________ > nix-dev mailing list > [email protected] > http://lists.science.uu.nl/mailman/listinfo/nix-dev > > -- Tomasz Czyż
_______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
