Replying to Avatar Signet

The reason this helps the Signet project is because it means being able to develop the code without having to wait for hours to compile the cross compiler and cross compile the libraries. Instead, we have a fast, reproducible way to get the the libraries that are either grossly outdated in the official repo, or don't have any package at all in that repo.

#SelfSufficency #OpenSource #dev

nostr:nevent1qqsqq88v0ph6neqrft6fyher78edxdsuwajtc5ykmccaf83v9fur8espz4mhxue69uhkummnw3ezummcw3ezuer9wchsygyckg2msm4e7sydvmqrygkymt7tu4e3ue9azaxea04z4fdj3exf4upsgqqqqqqsxeelru

Avatar
Dr. Hax 5mo ago

To give you an idea of the amount of time we're talking about here, the estimate on the build for this library is 5 hours.

If the something goes wrong (I used the wrong flags, the wrong include path, the wrong architecture, something unknow but it not worky, etc.), that's 5 hours wasted.

Not only that, but it means that I'm constantly taking long breaks and going off to do other projects. It's friction like this that is how people can easily get too many started projects and not enough finished ones.

nostr:nevent1qqsyxkv7hxtfww24ay4cyuaaghhccp3udv4th6v658s45ut0r3p2d8gpz4mhxue69uhkummnw3ezummcw3ezuer9wchsygyckg2msm4e7sydvmqrygkymt7tu4e3ue9azaxea04z4fdj3exf4upsgqqqqqqs0yr29c

Reply to this note

Please Login to reply.

Discussion

Avatar
Dr. Hax 5mo ago

There is, of course, a chance that these .deb packages won't pan out the way that I expect and all this excitement will burst like a huge bubble.

However:

A. At least there's *some* hope, whereas I knew what I have been doing it doomed to have to be repeated over and over, and

B. They're extremely simple packages and the one I spot checked looked like what I expected

C. I am using the code from the package that does have some .deb packages, so presumably this code produced some of the packages I've been using all along

So I'm still feeling optimistic.