> merely pulling in Nixpkgs is an effort, due to the repository being massive.
I've embraced daily shallow clone/fetches and the burden is now mostly just the 2GB of disk space.
It's a bit annoying though that git doesn't make it easier. No one would shallow clone later screw up and download every commit anyway, I feel shallow clone repos should be set up with a different configuration that fully-embraces shallow history (not that the configuration options even exist today AFAIK).
Interesting, I have taken a stab at maintaining a repo on the nixpkgs and using a --sparse approach, i.e. `git clone --filter=blob:none --sparse --branch nixos-25.11 https://github.com/NixOS/nixpkgs.git nixpkgs-dorion
cd nixpkgs-dorion`
Oh, maybe I had a full clone on my laptop before I started doing shallow fetches, but since fetching takes quite a while I've been using a shallow clone on my workstation.
I've only been doing this for a few weeks, so too early to tell if it's a good setup, but I added a GitHub Action that rebases my personal fork atop nixpkgs-weekly. I'm hoping that will help keep me from having a stale-by-default personal nixpkgs. (I use a personal nixpkgs to stage PRs waiting to be merged upstream.)
I remember thinking about doing that, but found value in having my fork tell me when was the last time I synced with upstream which was something useful to assess if I wanted to rebase my patch once again. Eventually my change got upstream and I stopped tracking my own fork though.
I started doing it this way (auto-rebase) when I started sharing one home-manager config across different devices.
This lets me do `nix flake update` on my home-manager config to have all my in-flight patches + the canonical nixpkgs from any device, and trust that they can all see the shared GitHub to sync. Hopefully will make updating less of a chore.
Only time it's bit me so far was when godot3 was broken in nixpkgs-weekly but worked in 25.11. Forced me to go write a PR for that and get it upstream to get my build working again, but that was more of a nixpkgs-weekly problem than a personal fork one.
One of the wrinkles of getting home-manager going on a bunch of different devices is that it liked to copy my local git checkout of nixpkgs to /nix/store a lot. That's why I'm preferring to have flake.lock point at my github.com branch, and then I can test uncommitted changes as-needed by passing --local to my home-manager switch incantation:
Are you building your systems on that auto-rebase? I've found that slight differences made my own fork not build for all my systems and gave up on having a personal canonical version (after I got things upstreamed). I let my machines update on their own schedule and keep track of the lockfiles through backups, in case I want to sync with a system that was built more recently (and hopefully will also build)
I have been. Hoping it cuts out some of the manual work and prevents me from accidentally writing a PR against an obsolete nixpkgs. The only changes I've made are ones I'd want to be upstreamed. So from the point of view of my individual devices, it's basically the same as just putting nixpkgs-weekly in my flake. I can nix flake update to pull changes into nix, and hard reset to update my local repo (which is now just an easier way to fast forward + rebase/cherry-pick).
We'll see how it goes. So far, it was broken upstream once when gcc was upgraded out of sync with godot3, and it looks like sublime-text might break next week do to an openssl change. But those are both artifacts of depending on weekly. If it stays this hairy, maybe I'll end up using the biannual release channels.
Is there footage available? A fully attentive human could've read cues from the environment and maybe avoid the accident or at least increased the error margin for that emergency stop.
If that wasn't an option I guess a fast reacting driver would have done a bit worse and an unattentive driver might have even ran ever the kid.
I find it ridiculous that airports in the US close. I've landed earlier than expected and you need to stare at the ceiling until 5am while other aeroplanes arrive and prepare for a race through customs.
I sometimes fly out of a small, local airport that only has one commercial route, from that airport to Philadelphia. That airport closes down overnight and it's perfectly reasonable. (And they open up at 5 AM to start serving passengers boarding the 7 AM flight; again, perfectly reasonable since there are 50 seats on that plane and you get through security in 5 minutes). But a major international airport that has incoming flights all night long? I agree, they should have at least ONE customs location staffed somewhere in the airport, any time an international flight is scheduled to arrive.
P.S. It's not just America. I flew through the Middle East once on my way to eastern Asia. The flight landed at something like 3:30 AM local time, and the security checkpoint didn't open until 4 AM or 5 AM or something like that. There were so many people waiting in line for that checkpoint, it was getting dangerously overcrowded in that hallway, with more and more people arriving down the escalator all the time. Thankfully nobody fainted or fell, but it could have been a bad situation there.
Not only US. A friend’s flight was late and about to land in Munich after the airport closes. So they had to land at a different airport and then take the train to Munich.
Long Beach does something similar; I did a training flight there and we left right as it was closing, when my wheels left the runway all the lights went off.
Not really - EV regen is really good. Even on my 4000 pound Fusion Hybrid, I don’t brake as often as I would in a gasoline powered vehicle because I’m able to coast down on the motor braking itself.
This is a software, not a hardware problem. Suitably intelligent software could gently apply the brakes every now and then in addition to regenerative braking even when it doesn't need to, just to keep the brakes in good condition.
The better you get at this, the more you'll drive around without getting the break pads checked.
This also increases the risk of running out of braking power when the car needs it the most, you'll be fine on an easy drive and then rear end the car in front of you or worse.
Are you sure it's the corporate tracker? Maybe it's the copilot tracker, or maybe the Recall video recording? Maybe it's the Windows anti-virus, or even the corporate anti-virus. What about the Advertisement stuff and the web search?
It's hard to tell what makes a non-stock Windows install slow.
The supreme court is under a DoS made of a spike of illegal decisions and is giving the appearance that there's no law to be followed. What an awful failure mode no one reasonable was capable of anticipating. Same with gun laws, now the tyrants have big enough guns that your personal 9mm can't deter tyranny
> Same with gun laws, now the tyrants have big enough guns that your personal 9mm can't deter tyranny
The fetishization of individualism is the problem here.
The guys who wrote that were fresh off a revolution where they had used privately-held arms to drive off a system of government. They didn't do that alone. They had committees on security and correspondence that would coordinate how arms were used. They were militias, not necessarily state-backed ones, either.
What you see now is a lot of people who are almost as well-armed, personally, as the tyrants, but not as well-organized.
reply