| @jreed:matrix.org | Playing around with pdebuilder. It's easier to set up. Problem is stx repos aren't organized the way debian packages are expected to be. There's a nested "deb_folder" inside of the usual "debian" folder. It's clear to me now that the build system copies source to a intermediate folder that is properly organized and then runs dpkg commands to build. Unfortunately, I just haven't been able to replicate it yet. | 14:11 |
|---|---|---|
| @fungicide:matrix.org | if you're building via the pdebuild command from pbuilder, be aware that it's mostly just wrapping the debuild command from devscripts (just inside an isolated chroot) so behaviors will be the same with regards to what directory structure it expects to find | 16:42 |
| @fungicide:matrix.org | and debuild is in turn a convenience wrapper for dpkg-buildpackage, yes | 16:43 |
| @fungicide:matrix.org | the documentation for each of those (manpages at least) should hopefully be helpful | 16:44 |
| @jreed:matrix.org | I think the build system stx uses is the dpkg-buildpackage. | 16:44 |
| @jreed:matrix.org | It's just a lot to read if you've never done it before. | 16:44 |
| @jreed:matrix.org | TBH... most people I grew up with are messing with deb packaging. But, I can respect its place in the world. | 16:45 |
| @jreed:matrix.org | * TBH... most people I grew up with are not messing with deb packaging. But, I can respect its place in the world. | 16:45 |
| @fungicide:matrix.org | oh, it's absolutely a lot to read. when i first started doing debian packaging about 20 years ago, it took me months to really get a solid idea of what was expected. though things have changed a lot in the last two decades, and there are new tools (mostly built on top of the older ones) to try to make things simpler | 16:45 |
| @jreed:matrix.org | Anyway... I was kinda told to put what I'm doing with this on hold pending some decisions. :/ | 16:45 |
| @fungicide:matrix.org | makes sense | 16:46 |
| @jreed:matrix.org | All I know, is (short version) .... I can't easily do it. 😅 | 16:46 |
| @jreed:matrix.org | Or should I say... cannot easily do it the way the repos/build-system are currently organized. | 16:47 |
| @fungicide:matrix.org | yep, there's no "easy button" (for correct distro packaging anyway) | 16:47 |
| @jreed:matrix.org | What gets my goose is that a large chunk STX software need not be "built into the OS."... could be containerized or packaged with python and pip-installed. But NO! Everything is a debian package.... | 16:48 |
| @fungicide:matrix.org | you can crib something together with the underlying toolchain to make something that will install and mostly work, but if you don't understand the design fundamentals for the distro, its packaging policies and the reasons they exist, et cetera, then there's a distinct risk the packages you're distributing can make a mess or even destroy the system they're installed into | 16:49 |
| @jreed:matrix.org | is a house of cards of sorts.. | 16:49 |
| @fungicide:matrix.org | well, it's an ecosystem of thousands of volunteer developers cooperating to maintain the largest linux distribution in existence with support for more processor architectures and translated into more languages than any other. and that sort of scope necessitates a lot of coordination and policy | 16:51 |
| @fungicide:matrix.org | and its inception pre-dates the modern container ecosystem by decades | 16:52 |
| @fungicide:matrix.org | so has solved many problems that people who are trying to build container-based solutions today don't even realize got solved many years before, and don't realize are even important to solve until the time comes that they're crushed beneath the weight of them | 16:54 |
| @jreed:matrix.org | That has been made abundantly clear to me at every corner. Thank you. | 17:28 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!