|  | Commit message (Collapse) | Author | Age | 
|---|
| ... |  | 
| | 
| 
| 
| 
| 
| | Previously, arguments to fupdate were also passed along to the update
script, they should now be filtered out. If passing them along is
wanted, they can be put behind a `--`. | 
| | 
| 
| 
| 
| | The check ran the update script if `--no-script` was specified and did
not run it, if it was not. | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| | This change allows to me to faster add new nixpkgs versions. | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| | This never really worked and would only really be useful, if I merged
things by hand.
But the only way forward, I see right now, is paved by avoiding the need
to merge stuff altogether. | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| 
| | They got themselves removed from Mozilla's Add-on store. To update the
extensions, I know need to remove them temporarily until the situation
is resolved.
Relevant issue: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/89 | 
| | 
| 
| 
| 
| 
| | The flake output `legacyPackages` is not actually “legacy”, it's just
nested. Thus, the output exporting the overlayed `pkgs` should be named
`legacyPackages`. | 
| | 
| 
| 
| 
| | That makes it possible to use plain `nixpkgs-unstable` for the whole
system, whilst still using my unmerged modules and packages. | 
| | |  | 
| | 
| 
| 
| 
| 
| | This project was hosted as a separate git repository. It is now
vendored, like the other projects directly associated with the
configuration. | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| | This makes reviewing (and closing) opened firefox tabs easier. | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| | 'l' is already taken. | 
| | |  |