Dependency on multiverse package

Asked by Kentzo

Hi,

We're about to package our proprietary application that has a dependency only available via multiverse package (VirtualBox 4.3.x)
I know that some users will disable this feature and I wonder if that will prevent them to install our app from USC.

In other hand, since our package is proprietary, won't it end up in the multiverse repo, so that problem will not exist by definition?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu software-center Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

I suggest you report a bug

Revision history for this message
Kentzo (kulakov-ilya) said :
#2

actionparsnip, you mean to reach right person to answer the question?

Revision history for this message
Launchpad Janitor (janitor) said :
#3

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Revision history for this message
Kentzo (kulakov-ilya) said :
#4

Anyone?

Revision history for this message
Manfred Hampl (m-hampl) said :
#5

Under which license do you intend to publish your "proprietary application"?

see also http://www.ubuntu.com/about/about-ubuntu/licensing and https://help.ubuntu.com/community/Repositories

Revision history for this message
Kentzo (kulakov-ilya) said :
#6

A proprietary license.

Links above does not answer simple Q: if I publish my proprietary application via Ubuntu Software Center, does it guarantee that users who are able to to install has multiver enabled and will be able to resolve VirtualBox 4.3.x dependency?

Really, it's completly unclear how apps are really distributed via USC.

Revision history for this message
Kentzo (kulakov-ilya) said :
#7

By proprietary license I mean that for the most parts of the application source code will not be disclosed.

But that's not what I'm worrying about: our software requires VirtualBox 4.3, which is only available in the multiverse repo which in turn may be disabled.

So we really have 2 options:

1. Pack VirtualBox
2. Ensure that our app will be in the multiverse repo which will implicitly make VirtualBox dependency resolvable.

We want to go for 2nd option, since we believe Ubuntu maintainer's will do better job by making installation of VirtualBox smooth. But I cannot get that simple answer :(

Revision history for this message
Launchpad Janitor (janitor) said :
#8

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Kentzo (kulakov-ilya) said :
#9