[Nix-dev] Tracking upstream releases

[Tony White]

On 11/08/2009, Michael Raskin <7c6f434c at mail.ru> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>
>
>  Ludovic Courtčs wrote:
>  >> Or do we want to add kind of scripting language to extract updates from
>  >> *any* kind of html page presenting download links?
>  >
>  > IMO (and as discussed at
>  > http://thread.gmane.org/gmane.linux.distributions.nixos/2421) there
>  > should be a `meta.watchURL' attribute (or similar) specifying a regexp
>  > of URLs to be watched.
>
>
> I have written (for my own needs) some Lisp code for comfortable
>  extraction of urls (or what not) from a relatively regularly structured
>  HTML page. It allows to express the condition in terms of page layout
>  per se, not by regexps which have own problems for complicated parsing.
>
>
>  > A dedicated tool, say `nix-watch-releases', would use this information
>  > to inform package maintainers of the availability of new upstream
>  > releases.  However, it'd be up to the package maintainer to actually
>  > test and commit the updated package, to avoid "automated breakage".
>
>
> Yes, I also think that commit-or-not should be a human decision. Or - in
>  any case - not Nix'es decision, it should be external tool anyway. If we
>  abandon reproducibility, why use Nix?
>  -----BEGIN PGP SIGNATURE-----
>  Version: GnuPG v2.0.12 (GNU/Linux)
>  Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
>  iQEcBAEBAgAGBQJKgcPdAAoJEE6tnN0aWvw3VJkH/jINtJ9uUzdltztTSdnOcFIJ
>  ch9Ccqo09qd9/sbO/uOwMB9nkXRAt9RDjKaGSCJxOxWCQOaM13eQTiz1MUctTrgq
>  K8EWumPdNtEpAFKTl+OocMYGaX8W5p93bJl93xyxpCnViQV/Lchs3RPANWy5UBPb
>  BmfGe5urWRRf8IeGfUQtSF86+C256Lt3d4oiM8wYWPOuaMkyYxoqT8t7yKAZIEqP
>  rL7FN6VjugWKT1MP9I5VDh/2HxEIl5XlmPLQHhGo2lIRCdU9GcfTa3jgP77RghfF
>  H21/y8QBWx7mvMTWKUgqBrY3tfPG4SpOoAXEqBO0vxsA04gvqW/KT1Su9t+T6+M=
>  =4jQm
>  -----END PGP SIGNATURE-----
>
> _______________________________________________
>  nix-dev mailing list
>  nix-dev at cs.uu.nl
>  https://mail.cs.uu.nl/mailman/listinfo/nix-dev
>
Hi,
I would like it to be a default fall back option in all package
expressions on failure (But I also want world peace) And it to also be
an option that can be switched on to be used by default instead of a
fallback, sort of like a bleedingEdge = true; switch in
configuration.nix.
In that case all the package expressions would grow because there
would be two entries for the source in the same expression and it
could even be an idea to add some way to pull the expressions
compressed as an archive and then decompress them before nix gets to
work on them.
I don't think it would be good at all to abandon reproducibility.

Thanks,
Tony