Announcing "Package" - The future default package manager for Potabi Systems.

"Wait, don't y'all already make the KIS package manager?" Well, no. KIS is not a package manager, it's a standard for custom package managers that happens to be working on a KIS implementation as an example. Here is the deal, there seems to be a misconception that package management systems for Unix-like systems (including Potabi) should be the same as everyone else. "Everyone should use Snap!" "No, use AppImage!" "Wait! No! Use Flatpak!" "RPM is perfect." "APT has the best packages!" etc. 

First, let's make it clear. Flatpak and AppImage will be supported, because they are popular technologies. Second, the FreeBSD "pkg" package manager will be in Potabi for a long while, until Package can be built with a large set of packages. Lastly, no, the name "Package" isn't directly from FreeBSD's "PKG".

Second, we will not support Snap's, APT, RPM, or other package managers. For some strange reason, Linux systems are using other distribution's package managers. The Ubuntu package manager, known as "Snap", is sold as a cross-platform package management solution, which is bad. The KIS standards is to help make more distributions independent, because package standardization can mean the Linux operating system derivatives don't share their package managers.

Third, why the name? We named "Package" as it is so it can be easier to remember the command. "Snap" is generally easy, but also for new users, just having it be "package" makes it so when someone needs to install this-application-software, they run "package install this-application-software" instead of worrying about a fancy name, acronym, or anything like that.

Package will replace PKG on Potabi in the near future, and it will be how our build system adds packages. We will also eventually remove ports from being preinstalled, but package will have a commands like "package --pull-ports FreeBSD", "package --from-ports this-application-software" if they want to use FreeBSD ports, it will also include support for other ports software, including custom, as long as it has a URL to install from.

Comments

Post a Comment

Popular posts from this blog

Where BSD Fails, and Potabi Aims to Succeed: Websites

Image
Welcome to a new series of articles I will aim to support called "Were <thing> Fails, and Potabi Aims to Succeed", where I mention specific issues plaguing Linux, BSD, etc. With Potabi and CoreNGS being replacements to BSD and Linux, read Potabi's Biggest Misconception: It isn't BSD. if you haven't because it explains that we are not a BSD, just BSD-derived. When we say websites, I mean ALL websites. I will only be doing active-development BSD-branded operating system websites for most of the big name BSDs, meaning not HelloSystem, AiryxOS, TrueNAS, TrueOS, FuryBSD, etc. Specifically we will critique DragonFlyBSD, NomadBSD, OpenBSD, NetBSD, FreeBSD, HardenedBSD, and GhostBSD. SoloBSD uses a blogspot for the main website, so I will ignore it. I want to explain why web-design is so important, and how it is often done wrong by the BSDs, and even many Linux distros. And what Potabi does to try and fix it. I am not trying to harass these operating systems, even...
Read more

Potabi 1.0 Dev Log: The Final Tasks

With the recent release of Beta-4 1.0A, Potabi is well on its way to being ready to release to the public. Beta-4 was a very difficult release to manage, especially with the concerns of our new ports system. What's in store for Potabi 1.0? What else is left to do? What are the last 3 betas? When are we dropping the A? What will be the final preparations for 1.0? What is Potabi 2.0 going to look like? Potabi 1.0 will essentially be very minimally different to our model: FuryBSD. I wanted to clarify something. No, Potabi is not "based on GhostBSD" as people like RoboNuggie in his 2-for-1 video you should 100% watch, even with this small mistake. That doesn't mean GhostBSD should gain no credit, since its builder is so similar to FuryBSD's, we actually did use some code and files from their project to fix certain issues we were having with FuryBSD's builder. Potabi 1.0's goal in release, as development continued, became less about "getting something per...
Read more

Linus Tech Tips PROVES WHY POTABI HAS A MARKET

Image
I remember someone telling me "You are foolish to attempt to redefine and redesign all of Unix and Linux." A few said "Linux is easy enough already, why change the fundamental core of what makes Linux, Linux?" And I still get comments "You don't give Linux enough credit in the ease of use and simplicity of the systems we all make." Potabi Systems has always aimed to be a show stopper. A system to give true freedom, and push stability. Change the core of every little detail, and tweak it to make a properly easy operating system. I am no stranger to r/LinuxSucks on Reddit. The current ideology of Potabi was born to move past the lies of Linux, and be honest where we have pitfalls, and make an operating system that  truly works to be a newbie friendly operating system - even if it might take many releases to get there. I shall not step down from my marijuana  appaloosa (high horse, get it?).  Okay, so what the honest to the gods' hell am I talking abo...
Read more