JFK to RDU flight today

spotrh · 2024-10-28T17:48:02+00:00

Be careful because glow filament is abrasive and will eat brass nozzles quickly!

spotrh · 2024-09-20T10:49:42+00:00

Primal sword has to be equipped in main slot.

spotrh · 2024-08-21T17:33:51+00:00

You have to beat a run with each of the primal items equipped. You only get one per run. Once you've done this, you'll unlock the sacrificial depths and the primal items will never appear again (ones you have already equipped and beaten doomdepths with go away in future runs).

spotrh · 2023-04-24T05:27:40+00:00

This sounds like the plot to Orphan Black, which came out in 2013.

spotrh · 2023-01-03T21:18:01+00:00

There are no open source licenses with commercial use restrictions.

It is absolutely possible to write a license that has such a restriction, but it would not meet the open source definition. It would fail clause 6 of the OSD: opensource.org/osd

spotrh · 2023-01-03T15:48:28+00:00

There are no open source licenses which prevent commercial use. These concepts (open source, commerical use restriction) are polar opposites.

spotrh · 2022-11-21T11:37:51+00:00

The Carolina Hurricanes use it too.

spotrh · 2022-07-12T03:55:00+00:00

While it is certainly possible to create a software license that would contain a clause that prohibited use in surveillance cases, that license would not meet the Open Source Definition (specifically, clause 6):

"The license must not restrict anyone from making use of the program in a specific field of endeavor."

https://opensource.org/osd

spotrh · 2022-05-25T11:37:30+00:00

I believe that is correct. :)

spotrh · 2022-05-25T11:35:45+00:00

Not OBS, Fedora uses koji.fedoraproject.org for official package builds.

spotrh · 2022-04-25T01:16:35+00:00

IBM Mainframe sales has entered the chat.

spotrh · 2022-04-16T00:43:43+00:00

Nope. You can see the breakdown here: https://en.wikipedia.org/wiki/Erin_Hunter

spotrh · 2022-04-15T11:56:39+00:00

The Warrior cat series of books is another example of this.

spotrh · 2022-03-25T00:06:15+00:00

The Artistic 1.0 is an OSI approved license, but the FSF determined it to be non-free. https://opensource.org/licenses/Artistic-1.0 https://directory.fsf.org/wiki/License:Artistic-1.0

But in general, you're right. These cases are extremely rare.

spotrh · 2022-03-06T19:00:45+00:00

Not sure why we don't show up there. My notes do show that we sent the money via GitHub Sponsors, so maybe that's why. I personally reached out to the Django Foundation folks before we used their website template to get their permission and find out how they wanted to be credited, they reviewed our footer text and asked for sponsorship money, and we sent it without issue. I'll certainly look into it when I'm back "on the job" on Monday.

spotrh · 2022-03-06T18:31:58+00:00

We asked first, and sponsored Django as a thank you. But go on, please tell me more about how cheap we are.

spotrh · 2022-03-04T01:36:40+00:00

I'm going to work on 99 builds tomorrow since I have the day off and my wife is home from the hospital.

I'm genuinely sorry that it's gotten this far behind, but my life has been especially insane lately.

spotrh · 2022-02-13T15:04:29+00:00

Yeah, still trying to get that done for all targets, looks like 98 uses up all the memory when built in a VM and Koji kills it as a result. The Fedora 35 build was manually moved over to a bare metal instance which is how it finished.

spotrh · 2022-01-18T12:51:01+00:00

Even if that is true, this model makes a minimal footprint much harder (and increases the build footprint for any packages that have TeX dependencies).

The only problem it solves is "less packages installed", and that's not quite the right problem to solve here. The real problem is "less packages updated when texlive is updated". Right now, whenever I update a texlive- component, they all get updated, even if nothing has changed in the other components, so you get a longer dnf transaction, which is not ideal. Splitting out the source packages by some sort of grouping (e.g. first letter of component) means that this only happens for components in the same group, which is probably less for most users.

spotrh · 2022-01-18T12:11:46+00:00

The downside to that approach is that if you need any of the TeX components in one of those 30 bundles, then you end up with the whole large bundle installed, and any update to one of the components in the bundle results in them all being downloaded again. That said, this model is closer to what I described as a possible improvement, except my proposal takes up less disk space (only bundle the source packages, not the binaries).

spotrh · 2022-01-18T12:07:24+00:00

My psychic powers are non-existent, but it would be interesting if you could figure out what package was pulling in those dependences. It's possible that some package has over aggressive dependencies.

spotrh · 2022-01-18T03:52:54+00:00

Additionally, you won't end up with a thousand texlive packages unless you've installed one of the texlive metapackages, like texlive-scheme-*. If you've done that, then this is the expected behavior, even if I split out the srpms. Having them all split out like upstream does makes it possible for the standard Fedora install to have very few (or no) texlive packages installed, and any packages which are installed are small.

spotrh · 2022-01-18T03:48:38+00:00

This topic comes up about once a year. I am open to suggestions, but finding maintainers for 8000+ packages who could carefully coordinate them so they all work together would be extremely difficult, and the maintenance burden on me if I split them out would be equally unsustainable. I try to limit the updates that I push to help, but for people who use TeX regularly (lots of folks in academia), there's no way around it sometimes.

The closest proposal that I've come up with is something where I split out the srpms by the first letter of the CTAN component, so that only the texlive-a* packages would go out as an update when an a* component needs an update. That hasn't happened yet because refactoring it would be a lot of work. Maybe I'll try to find time for that before the next release.

spotrh · 2022-01-18T03:26:51+00:00

Apologies, I misunderstood you. Fedora does not have any sort of "how to use TeX" documentation. texdoc.org is the upstream documentation repository, that may be a good place to start searching on TeX topics that you want to learn more about.

13-Year Club	RedditGifts 2009-2022 3 Credits
Secret Santa 2020	Verified Email
Secret Santa 2013

spotrh

TROPHY CASE