go away stupid frognigger

>>109027918
is there a guide? LFS doesnt count

File: 1439230034303.jpg (7 KB, 250x239)

7 KB JPG

>>109027921
no
>>109027943
>LFS doesn't count
it's the perfect guide to get started to build your own distro

>>109027943
NTA, but I usually do this, except OP is likely a liar, because building a working system will require a lot of work. I have a 'package manager' that's just a bunch of scripts to build and install in a local directory. But building libbsdwhatever.so.3 or libgtkfuckyou3.4.so.1 isn't really fun and it takes days to download all the correct working versions and make sure they work with the rest of your system, which may require patching.

Usually I start with a linux recovery, or a a debian iso, as they have all the tools to setup networking, format disks, setup a chroot and start compiling. I think even lfs/gentoo recommend starting from a debian iso as it has all that's required for setting up the system.

But realistically, even if you're working on it 24/7, there's no way you'd be able to package and maintain all the software required for a simple rolling system. So at some point you look into repositories, which kinda force you to use their crap. I like debian because they have great quality repos, with source code available for all package via apt source. And in general I prefer dpkg over other alternatives as it just works and resolves conflicts nicely (options to do a diff-merge when files conflict)

>>109028542
>even if you're working on it 24/7, there's no way you'd be able to package and maintain all the software required for a simple rolling system
that's where you are wrong anon, it takes me 5 minutes per day, everything is pretty much automated. since you called me a liar here is my github with all the packages 100% up to date.
https://github.com/sauzerOS/sauzeros
the basis is I keep everything up to date to the latest version in my repo and if I need a package to stay on an older release my package manager can just checkout and build that older version.

>>109027918
Vibe coding doesn't count, tourist.

>>109029249
lmao AI is the perfect tool make a package manager and at least it's in a real language and not some python abomination like portage.

>>109029243
it's kinda cool, but you're not doing anything to mitigate compatibility issues.

your packages provide no information about what file/s are provided, making it almost impossible to uninstall a package.

also you don't seem to be separating regular libraries from devel libraries, nor are you applying security patches, or compatibility patches which all major distros are doing.

>make install
that is proof you don't know what you're doing.
that shit will happily destroy your environment. at least build some intermediary package that you can use something like gdebi to make sure it doesn't break your entire system.

>>109030204
note sure if you're trolling but
>your packages provide no information about what file/s are provided
hokuto manifest pkgname
lists all the files of a package
>making it almost impossible to uninstall a package.
hokuto uninstall pkgname
uninstalls the package
>separating regular libraries from devel libraries
useless minimalist retardation
>applying security patches
you don't need to apply security patches when your packages are up to date and if there are patches instead of version bumps I apply them (eg bash)
>make install
make DESTDIR="$1" install is not make install retard, also I build all the packages as a normal user to avoid rogue packages installing random shit outside of the destidir

>>109030274
I read your package manager code. And everything it does, it does poorly, disregarding common safety precautions.

I opened the install.go and uninstall.go and they're riddled with logic errors and bugs waiting to happen. Find another place to shovel your slop.

I must say, I had quite a blast looking at manifest.go. If any of the steps fail, then you're left with a broken system. LMAO

File: Screenshot_20260611_235121.png (2.16 MB, 2067x1035)

2.16 MB PNG

>>109030674
>broken system
yet I've been using my distro for 6+ months on my desktop + rpi4 (all packages cross compiled from my desktop) and everything works. For example if I have a root shell I can uninstall glibc, brick my system and recover by just installing glibc from my package mirror. And I could keep a static busybox around just to ensure I can always open a root shell for recovery.

File: Screenshot_20260612_001639.png (838 KB, 1313x650)

838 KB PNG

>>109030674
anyways thanks for the criticism, I noticed that my busybox wasn't statically compiled and that I didn't have symlink for ash in my package. I fixed both issues and as you can see I can uninstall glibc, open a root shell with busybox and re-install glibc from the remote mirror. most distros would not be able to recover from this without using a live environment.