* geogebra 6 : init at 6-0-598-0
since geogebra was ported from java to electron, this is a repacke;
wont want to delete geogebra 5, no darwin package for 6
ran nixpkgs-fmt over the file to cleanly reformat the spacings
Update pkgs/top-level/all-packages.nix
remove a trailing space
Co-authored-by: Tom Smeets <Tom.TSmeets@Gmail.com>
Update pkgs/applications/science/math/geogebra/geogebra_6.nix
Co-authored-by: Tom Smeets <Tom.TSmeets@Gmail.com>
Applied a sugestion for the formating of the lines
fixed a mistake, where the wrong name attribute was used
removed an unnecassary chmod statement
added a downlod link to archive.org
moved geogebra_6.nix to geogebra6.nix
removed unnecesary build inputs statement
* renamed to geogebra6
nixpkgs already has Inform 7, which is a lovely design system for creating interactive fiction (text adventures) using a natural language compiler and a rich IDE. However, underlying Inform 7 is a C-like language, Inform 6, which has a much simpler toolchain and its own compiler and standard libraries, which I have packaged for nix here.
* sile: reformatting, not changing drv at all
Put all inputs on separate lines and don't use `with stdenv.lib` for
large scopes.
* sile: 0.10.4 -> 0.10.9
Add poppler_utils as check dependency. Clean up some outdated comments
and hooks. Add more outputs for better closure size.
* maintainers: add alerque
* sile: add alerque as maintainer
Not strictly an upgrade, but adds a new mongodb-4_2 target with the
current mongodb from that branch.
Use matching client and server versions in mongodb tests- tests were
using the mongo 3.4 client to connect, and this finally doesn't work
with server 4.2.
Per reviewer suggestion, adding myself as cheetah3 maintainer.
Additionally, reestore comments describing the purpose of the
build-dependencies patch
This change was preceded by the idea of adding a pronoun field to the
file, which we determined to be a bad idea:
* maintainers-list: add pronoun to the optional fields
I often do not know how to address maintainers, so giving them the
ability to specify their pronouns is helpful for communication
purposes.
* maintainers-list: add pronoun for Profpatsch
maintainers-list: make the pronoun field into a list
Some people have a set of pronouns they are fine with, so let’s make
that possible.
Based on feedback by somebody With An Idea™ of the topic.
* maintainers-list: remove the pronouns field
The discussion around the field raised a good point, quoting:
> What you are proposing here is keeping an irrevocable permanent
> history of people’s pronouns. It makes anybody would want to do bad
> things with it one small script away from a list of which Nixpkgs
> contributors are trans. Even looking at the history of name
> changes (which we probably also shouldn’t store) wouldn’t be nearly
> as reliable a source. While it might be tempting to say that
> participating in this would be optional, it would be establishing a
> de facto standard location for this information, that might make
> people feel compelled to participate or accept having the wrong
> pronoun used. Compounding this is the fact that the people who will
> be most comfortable using this field are the people who have never
> changed their pronouns. If they decide to in future, they now have
> to choose between permanently marking themselves as somebody who
> changed or deleted their pronouns (which is dangerous) or leaving
> the wrong pronouns up. Because of this, I think that over time this
> list would probably result in even more people being referred to by
> the wrong pronouns, because of outdated entries that are dangerous
> to correct.
>
> **This idea is extremely dangerous**. If somebody wants to publish
> their pronouns, they can already do that on their website or GitHub
> profile, without having to include that information in a large
> public dataset with history tracking.
So let’s remove it again.
Honggfuzz is a security oriented, feedback-driven, evolutionary,
easy-to-use fuzzer with interesting analysis options. It is
multi-process and multi-threaded, blazingly fast when the persistent
fuzzing mode is used and has a solid track record of uncovered security
bugs.
See https://honggfuzz.dev for more information.
