https://github.com/mass1ve-err0r/wpkg
A kinda dpkg-deb for Windows
https://github.com/mass1ve-err0r/wpkg
debian-packaging debs packaging packaging-tool windows
Last synced: 12 months ago
JSON representation
A kinda dpkg-deb for Windows
- Host: GitHub
- URL: https://github.com/mass1ve-err0r/wpkg
- Owner: mass1ve-err0r
- License: mit
- Created: 2019-12-27T09:06:07.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2019-12-28T16:02:33.000Z (over 6 years ago)
- Last Synced: 2025-05-07T13:33:29.923Z (about 1 year ago)
- Topics: debian-packaging, debs, packaging, packaging-tool, windows
- Language: C#
- Homepage:
- Size: 20.5 KB
- Stars: 13
- Watchers: 4
- Forks: 5
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Windows Packager - wpkg
A kind of dpkg-deb for Windows, completely written in C#.
## Introduction
If you own a device running iOS and it's jailbroken, you'll know that additional software ("Tweak" or "Theme") is distributed through iOS specific APT repositories and are packaged as `.deb` files.
Unless you work within WSL, managing debian packages is a breeze. The only downside to WSL are its permission issues.
I wanted a WSL-free solution and that's how wpkg was born: A pain free dpkg-deb, completely written in C#, for the platform everyone is familiar with.
___DISCLAIMER: It's not entirely dpkg-deb, to be clear.___ This utility was mainly designed to help and make (jailbroken) iOS development easier on Windows. However, you can still use it however you may please!
__PLEASE READ THROUGH THE WIKI ([HERE](https://github.com/mass1ve-err0r/wpkg/wiki)) TO UNDERSTAND ITS TRIGGERS__
## Features
- Creation of `.deb` files
- Extraction of `.deb` files
- Custom triggers
- `--theme` to quickly create a skeleton base for creating themes
- More can be added to the official wpkg! (To request, feel free to create an issue or just recompile it yourself!)
## Installation Guide
*--This is the recommended method so you can call it from anywhere. Else you'd have to add it to the Windows folder directly so it's visible globally--*
1. Open a new Explorer Window, navigate to your Windows boot drive *(commonly "C")* and create a folder titled "_mytools". (The name is an arbitrary choice, just for good measure we keep it clear)
- The full path at the end should look like `C:\_mytools`
2. Open the Start Menu and searh for `env`. It should suggest editing the environment variables.
3. Once the Menu opens, select `Environment variables`.
4. Under System variables, search for `PATH` and edit it.
5. Add a new Entry
- An Entry in the `PATH` is always a path, so here our entry is `C:\_mytools`
6. Now that we have added our folder to the `PATH`, you can now just download it, move it to our "_mytools" folder and Ta-DA! It's now accessible from the commandline like any other tool!
7. Profit??
## Download
__! I CANNOT STRESS THIS ENOUGH: PLEASE READ THE WIKI IF YOU HAVE ANY ISSUES/ TROUBLES FIGURING OUT HOW THIS WORKS !__
Link (stable release): [HERE](https://github.com/mass1ve-err0r/wpkg/releases/latest)
Guide on commands: [HERE](https://github.com/mass1ve-err0r/wpkg/wiki/Command-Overview)
## Thanks/ Credits
- F. Carlier for dotnet-packaging - This was a tremendously good resource to study!
- OpenGroup for the gool 'ol `.ar` and the necessary header
- MSDN for providing the best C# support
- ICShapCode for SharpZipLib - you guys rock!
## License
This project is licensed under MIT.