Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ TheIDE » U++ TheIDE: Other Features Wishlist and/or Bugs » [EFFING PACKAGE MANAGEMENT] Provide cross-distribution of packages of U++ (https://github.com/jordansissel/fpm)
[EFFING PACKAGE MANAGEMENT] Provide cross-distribution of packages of U++ [message #47174] Sun, 25 December 2016 11:19 Go to previous message
MrSarup
Messages: 30
Registered: December 2016
Member

[EFFING PACKAGE MANAGEMENT] Provide cross-distribution of packages of U++[ 5 votes ]
1. Yes, I agree 1 / 20%
2. No, it does not matter 1 / 20%
3. Perhaphs it may be helpful 3 / 60%

Hi Mirek,

Mirek mentioned in the following thread here:

http://www.ultimatepp.org/forums/index.php?t=msg&th=9817 &goto=47171&#msg_47171
mirek wrote on Sun, 25 December 2016 09:52

Personally, I would prefer removing .spec file altogether.
.rpm based distros are Spanish village for me. IMO, our responsibility for nightly builds / releases should stop at producing tarball with makefile which builds (perhaps after some package installs) on any most targets. Platform specific packages should be out of ultimatepp.org responsibility...
There are too many target platforms to maintain directly...
Mirek


With your answer, you did surprise me a lot. To be able to make a good package requires placing the files in their appropriate directories on Linux platform. Many irresponsible developers do not read the following on Filesystem Hierarchy Standard and create chaos on each platform and system:

https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

"Making a good package" also means compiling the source code against the right versions of libraries.
Whenever a different source code is released, this may require different library. "Making a good package" means this step is included in there.
Further, is assures that things will work because _ONE_HAS_TO_DECLARE dependencies with the right package names in that binary. It will also include menu entries, MIME handlers, documentation, startup scripts, etc. as well.

By providing a spec file, you also allow users to obtain all facilities of rpm with a difference that you did not built them yourself and compel this dirty work to be done by an user. Thats fine. But the moment you declare that the spec file belongs to garbage, then many users may have problems.

Thus, I come up with a suggestion to provide cross-distribution of packages of UPP by using FPM technology. This is available here:

https://github.com/jordansissel/fpm

There is a good guide here:

https://www.digitalocean.com/community/tutorials/how-to-use- fpm-to-easily-create-packages-in-multiple-formats

If theIDE is cross-platform, why not packages for distributing its source code with cross-platform quality?

[Updated on: Sun, 25 December 2016 11:33]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [BUG REPORT] Renaming package has bugs. Introduce $PACKDIR as STD relative path
Next Topic: Splitting window + color(abbrv) bug
Goto Forum:
  


Current Time: Sun Jun 16 20:39:28 CEST 2024

Total time taken to generate the page: 0.02259 seconds