Maybe spend some time investigating how to make nuget packages and then move onto deb or rpm. That way you’ll have a better idea of the problems that you’ll face in making your own. Personally whenever I feel the need for some kind of package manager, nuget is flexible enough that I can repurpose it to almost anything.
I guess a good start would be to look at some minimal package managers like opkg. Maybe xbps, pacman too; the format is simple but for pacman you need rather look at libalpm.
You seem to be a very novice programmer.
how do I setup my dev environment
? Google that? Use a devcontainer? I mean literally a question answered thousands of times.
where should I start
Setting up your dev environment. Then maybe create a few projects for you to test your package manager empirically?
do I invent my own pkg format or do I use pre built packages like deb or rpm?
Depends on what you want to do. I’m honestly not sure how to help you here? What kind of answer are you fishing for here?
yes I am a novice programmer and don’t know much about c# either but I have made a bunch of projects which is fairly usable so I am not someone with no experience.
Why would you do that?
Aside from the fact there are so many package managers out there, don’t you want to start with something simpler?
Abandon microshit c#
Edit: also read apt/dpkg/rpm/yum/pacman source? Deb literally just tar with file with same hierarchy as in os with one or two extra file for metadata.
Slow down, relax, OP asked a question, not murdered your pet hamster.
Every package manager you mention is shit. Look at guix, nix or pnpm for better, innovative concepts and ideas and implement them better.
Every package manager you mention is shit.
And so are you.
Wtf, do you know nix, guix and pnpm? They have way better concepts, ideas and functionality then the legacy package managers you mentioned.