U++ forum: Welcome to the forum

Re: Splitting debs into two parts [message #26197 is a reply to message #26196]

Mon, 12 April 2010 08:21

dolik.rce
Messages: 1791
Registered: August 2008
Location: Czech Republic

Ultimate Contributor

nlneilson wrote on Mon, 12 April 2010 00:02

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.

1. There is JDK builder in Build methods. There is probably no documentation but you can have a look at uppsrc/ide/Builders/JavaBuilder.cpp.

2. Yes, that is what I mentioned in first post (in technical details). It is unlikely that only one of the packages would be updated, it would quite difficult technically. To provide binary instead of letting the user build theide is the whole idea of debian packages. But it has nothing in common with windows installer.

3. Source + application is the obvious choice, but there could be also finer-grained solutions (see mr_peds post above). Just for clarification: We are not in Debian distribution yet, we just publish packages in Debian format (actually only meant for Ubuntu right now).

Honza

Report message to a moderator