Skip to content
This repository has been archived by the owner on Feb 27, 2024. It is now read-only.

Call for Content: 2020/04 #115

Merged
merged 4 commits into from Apr 24, 2020
Merged

Call for Content: 2020/04 #115

merged 4 commits into from Apr 24, 2020

Conversation

domenkozar
Copy link
Member

Hi all,

please add Nix news item in form of:

- [Example news item title](http://example.com)

  Optional item description.

preferably as a PR against master branch (or a comment below).

Thank you <3

@matthewbauer
Copy link
Member

@davidak
Copy link
Member

davidak commented Mar 24, 2020

  • Announcing Marketing Team

    The marketing team was founded and had their first meeting. They already improved the website (see Learn page). If you want to join, you find the details in the announcement post. Let's improve the presentation of Nix/NixOS!

@domenkozar
Copy link
Member Author

@Mic92
Copy link
Member

Mic92 commented Apr 2, 2020

  • nix-update
    A tool for updating nix packages semi-automatically

@davidak
Copy link
Member

davidak commented Apr 3, 2020

Also mention that:

  • nixpkgs-update

    automatically runs now on nix-community infrastructure

ryantm/nixpkgs-update#13 (comment)

@Mic92
Copy link
Member

Mic92 commented Apr 3, 2020

Also mention that:

* [nixpkgs-update](https://github.com/ryantm/nixpkgs-update)
  automatically runs now on nix-community infrastructure

ryantm/nixpkgs-update#13 (comment)

I will add a FAQ to my project how nix-update is different from nixpkgs-update.

@bhipple
Copy link

bhipple commented Apr 4, 2020

It looks like you've only just recently started work nix-update in the last couple weeks. Is there any real reason to write a second tool that does basically the same thing as nixpkgs-update? Notably:

  1. nixpkgs-update does fetch release information from both github releases and pypi.
  2. nixpkgs-update also updates both Rust and Go packages.
  3. nixpkgs-update can be run stand-alone to update/build/test a single package interactively, or even send a PR for that one package in isolation, see this build/PR, which I ran as myself from a local feature branch checkout of nixpkgs-update: tflint: 0.15.0 -> 0.15.1 nixpkgs#82465
  4. nixpkgs-update does not have to send pull requests on its updates (see the --dry-run, which will just update/build/test/report locally).

It being in Haskell is a bit of a barrier to entry compared to Python, to be sure, but we're trying to improve the test suite, dry runs, logging, and interactive output story in particular to make it easier to integrate new rewrite rules for the updater. It'd be nice for us to combine resources and work together rather than splitting our efforts to re-implement the same logic. I've found @ryantm to be extremely active and helpful in accepting/integrating improvements.

@ryantm
Copy link
Member

ryantm commented Apr 4, 2020

Thanks @bhipple. I was thinking the same thing. At this point, the main hurdle I see to most people using nixpkgs-update interactively is the installation story. The issues with that are tracked here ryantm/nixpkgs-update#137

@ryantm
Copy link
Member

ryantm commented Apr 4, 2020

Currently, the nixpkgs-update PyPi and GitHub fetching only happens in batch mode, not interactively. Seems like a good feature to add though.

@Mic92
Copy link
Member

Mic92 commented Apr 5, 2020

It being in Haskell is a bit of a barrier to entry compared to Python, to be sure, but we're trying to improve the test suite, dry runs, logging, and interactive output story in particular to make it easier to integrate new rewrite rules for the updater. It'd be nice for us to combine resources and work together rather than splitting our efforts to re-implement the same logic. I've found @ryantm to be extremely active and helpful in accepting/integrating improvements.

Yes. ryantm's version did not really provided the workflow needed for end-users. My implementation is not really a loss for your project. I tried several times to learn Haskell but I don't understand its errors messages and documentation, so I would not contribute to your implementation much.

@marsam
Copy link

marsam commented Apr 5, 2020

- [Create and Publish a Website with Hakyll, HAProxy and NixOS](https://www.thomasbach.dev/posts/2020-04-03-website-init.html)

- [Declarative, Decentralised, and Secure communication via Matrix, Jitsi, & NixOS](https://kaushikc.org/posts/matrix-jitsi-nixos.html)

@Mic92
Copy link
Member

Mic92 commented Apr 21, 2020

@domenkozar
Copy link
Member Author

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants