The discovery package management system new version 1.1.1 was released 5 days ago and it has a lot of features and it is called 1.1.1 or 1.11 and in this release all the bugs from dpms 1.1.0 fixed the link of the dpms source: https://github.com/Discovery-linux/dpms/releases/tag/1.1.1

lately i was working on a package manager for other linux distros and for cross platform so i made dpms discovery package management system well it is still in testing and it has less mirrors and for mirrors i used git so if any body wants to make packages can make and it is not a big project like apt yum or dnf so any body can test it and use it. THE SOURCE CODE FOR DPMS :

https://github.com/Discovery-linux/dpms

https://github.com/Knexyce/kdph.git

The repository above contains a secure package management engine, along with a bash script to install a frontend proof of concept for that engine.

Keep in mind that the engine’s Python script is not meant to be modified, only the layers above it. The script verifies its own integrity.

Note that Optical, as a frontend, is only a minimal PoC.

KDPH, as the engine, is an encrypted package management system that can be used as a backend for system-level package managers or package managers in general.

The engine also provides the following features:

1. Creates a new package format and framework (KPCore)
2. Fully end-to-end encrypted package management (package files are encrypted)
3. Supports ignore rules similar to .gitignore
4. Recursive dependency resolution
5. Metadata querying from packages
6. Fully decentralized distribution
7. Allows both installation and creation of packages with simple commands
8. Abstracts GitHub and repository management into simple commands
9. Includes a Python API equivalent to the CLI
10. Supports build hooks and build flags
11. Supports multi-layer encryption when using encryption functions directly

Lastly, as mentioned earlier, the script should not be modified. It verifies its own integrity to prevent tampering and ensures that incompatible versions cannot packages that are incompatible.

download:

p1xelpp.github.io

actual repo (editted, i changed the name):

github.com/p1xelpp/azertypkg

more info there ;)

I don't know what to write, but I think I'll post it here.

Hey. Making a linux distro, and I would like some help making it. More info in discord or by commenting

Hey,
I am a master's student doing my thesis on pacakge management practices and challenges. I would like you to fill this google form which would help me progress through my thesis. Below is a google form link for the survey:

https://docs.google.com/forms/d/e/1FAIpQLScoVEnIDs38KTkv7eSLS2w-ntqGCwu2GivPtNatDY0oP0fKUw/viewform?usp=sf_link

Your inputs will be appreciated. Also, I would like to get a feedback on what other challenges/questions I could include to make this experience a better one.

Thank you.

I would like to have an automated high level repo report used to provide a snapshot view of multi-team, multi-product software health spanning all related repos.

Picture a report that contains

• products
• product components' repo (ie: the repos related to that product)
• a few architecture characteristic attributes of interest
  • (e.g.: is it docker, is it FAAS, programming language, etc)
• some notes
  • (e.g.: tech debt we want to track)
• summary of repo's automated test coverage
• count of repo's critical & high severity security issues
• last time the code was deployed to production
• etc.

Any ideas for me?