Home » Developing U++ » U++ Developers corner » Splitting debs into two parts
| Re: Splitting debs into two parts [message #26196 is a reply to message #26190] |
Mon, 12 April 2010 00:02   |
nlneilson
Messages: 644
Registered: January 2010
Location: U.S. California. Mojave &...
|
Contributor |
|
|
| Quote: |
1. "... (java should work out of the box ..."
2. Anyway, this is not the point of this discussion. The topic is how to best split the package to adhere to the packaging policies.
3. ... how to best split the package...
|
1. Interesting, are there any examples that show this?
2. Splitting theIDE from the source may work like many apps that are in the Ubuntu Synaptics. Selecting an item will automatically select the items it depends on, the user has the option of deselecting any of the additional items.
For a user that wants to try Upp then theIDE would be selected also.
An additional advantage would be if either the library or theIDE is up to date then only what needs to be updated will be downloaded.
One very important thing for a new user would be to have theIDE as an executable, 6.7 MB, rather than have them build it, that is just an extra hurdle that many may not even try or have problems with.
Looking at this from a different perspective, would it make sense to do away with the Windows installer and require a user to build theIDE. I don't think that would be a good idea.
Why make a Linux user build it??
3. Split theIDE from the source/library.
Send a proposal to whoever makes the decisions for what is to be included in Debian, whatever they accept or recommend seems to be the "ideal" way.
[Updated on: Mon, 12 April 2010 03:34] Report message to a moderator |
|
|
|
Current Time: Wed May 14 11:08:09 CEST 2025
Total time taken to generate the page: 0.02959 seconds
|
Members
Pages
Help
Register
Login
Home
