packagemaker | Simple tool to help creating packages

by ssato Python Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | packagemaker Summary

packagemaker is a Python library. packagemaker has no bugs, it has no vulnerabilities, it has build file available and it has high support. You can download it from GitHub.

Simple tool to help creating packages (rpm, deb, tgz, etc.)

Support

Quality

Security

License

Reuse

Support

packagemaker has a highly active ecosystem.

It has 15 star(s) with 1 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 2 have been closed. On average issues are closed in 4 days. There are no pull requests.

It has a positive sentiment in the developer community.

The latest version of packagemaker is current.

Quality

packagemaker has 0 bugs and 0 code smells.

Security

packagemaker has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

packagemaker code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

packagemaker does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

packagemaker releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

packagemaker saves you 3380 person hours of effort in developing the same functionality from scratch.

It has 7248 lines of code, 859 functions and 113 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed packagemaker and discovered the below as its top functions. This is intended to give you an instant insight into packagemaker implemented functionality, and help decide if they suit your requirements.

Parse a line of filelist
Parse a single string
Parse a string
Setup files
Checks if the node is a file
Filetype
Compiles a template
Search for a template
Update the contents of the scaffold
Find the owner of the given path
Date params
Generate a date
Returns a dictionary mapping of the built - in type
Predicate predicate
Return the default type

Get all kandi verified functions for this library.

packagemaker Key Features

No Key Features are available at this moment for packagemaker.

packagemaker Examples and Code Snippets

No Code Snippets are available at this moment for packagemaker.

Community Discussions

Trending Discussions on packagemaker

MacPorts: "Error: clang-4.0 has been replaced by clang-8.0; please install that instead" but I have clang-8.0 already installed

What are the risks of doing my own cross platform (Win + OSX) installer?

QUESTION

MacPorts: "Error: clang-4.0 has been replaced by clang-8.0; please install that instead" but I have clang-8.0 already installed

Asked 2019-Jul-27 at 02:11

I am getting the same error when trying to install many ports with MacPorts, e.g. gtk2:

...

ANSWER

Answered 2019-Jul-25 at 04:10

This is an obsoletion message. Since you already have the replacement, just uninstall clang-4.0, llvm-4.0, and lldb-4.0 and you will be fine.

Source https://stackoverflow.com/questions/57162325

QUESTION

What are the risks of doing my own cross platform (Win + OSX) installer?

Asked 2019-Apr-16 at 15:48

I have a quite complicated build process involving different directories (for plugins) ; currently using NSIS on Windows and PackageMaker on OSX but have issues improving them as my install / uninstall process is getting more complex with time.

The more I look into it, the more I feel like I should code my own cross platform installer with a cross platform GUI like wxWidgets (I've used it before) and copy myself the right files in the right directories because I cannot find any good cross platform software installer OR even programmatically customizable software installers for both platforms.

Has anyone gone down that path ? Does anyone know what are the hardest things to achieve, blocking everyone to produce good softwares installers and why doesn't this exists right now ?

Thanks in advance!

...

ANSWER

Answered 2019-Apr-16 at 15:48

Does anyone know what are the hardest things to achieve

The hard part about installers is not wizard GUI, it’s OS integration. That integration is dramatically different across OSes.

On Windows, you need to use MSI. NSIS doesn’t do particularly good job, MSI enables repair/modify functionality, by default MSI can upgrade stuff even when old version is still running (and it continues running while being replaced), some MS libraries ship as *.MSM merge modules… BTW, I usually use WIX for that.

Similarly, on Debian and Ubuntu Linux you need to create .deb packages. Even if you’re making a GUI installer. They also support repair & upgrades, versioning, dependencies, but they do it in completely different way than MSI.

I don’t have much experience with OSX but I think it has some other installer infrastructure implemented by the OS.

Source https://stackoverflow.com/questions/55704850

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install packagemaker

You can download it from GitHub.
You can use packagemaker like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: