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

In Response to the Odysee Team on Their Derogatory Tweet.

Image
On December 14th, the Odysee team - lead by the LBRY, inc. known for their harassment and disregard for professionalism - posted an announcement for job openings for Autistic workers. The Tweet is extremely derogatory in nature.    The Tweet, which reads " In Q4 we tripled the hires of women at odysee If you're autistic and want to work with hot babes check out some of the roles we're recruiting for here." This comment is unprofessional, derogatory, and borderline sexual harassment of the women who chose to work there. The comment of "wanting to work with hot babes" as the main inspiration for supporting the platform in hard work, and trying to convince autistic programmers to join the company based on a sexually degrading comment is absolutely unacceptable. The Open-Source community needs to stand against sexually harassing comments, advocating the hire of employees based on sexual exploitation. Don't use the bodies and perceived "hotness"
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

Potabi's Biggest Misconception: It isn't BSD.

As the lead developer of Potabi, I take full responsibility for fucking this one up. However, we are actually not a BSD system, it's supposed to be (long-term) a new UNIX branch all together, away from any BSD's. Potabi will later include bits and pieces from all sorts of operating systems, including (but not limited to) ReactOS, Illumos, Linux (clones of what they do at least, because of Linux's borderline-abusive license), HaikuOS, Minix, SerenityOS, and others. So Potabi plans to basically rework everything in FreeBSD long-term? Why? Instead of taking the SerenityOS route and doing it 100% from scratch, we are going to utilize open-source software that already exists to give us a short term boost.  But wait, isn't Potabi a "better FreeBSD for desktop and mobile"? Wasn't it a mobile OS? Yes, yes, but also, it's complicated. Potabi was originally just a way for me to get a better mobile OS , then it became bigger and bigger. It has long since not be
Read more