On 05/01/2015 01:20 AM, Adam Williamson wrote:
On Tue, 2015-04-28 at 15:15 +0200, Jan Chaloupka wrote:
Is there a minimum requirement what should a common package provide
or
is it just arbitrary?
There's no real requirement. Personally 'common' is the name I'd most
likely expect, with one
On Tue, 2015-04-28 at 15:15 +0200, Jan Chaloupka wrote:
Is there a minimum requirement what should a common package provide
or
is it just arbitrary?
There's no real requirement. Personally 'common' is the name I'd most
likely expect, with one proviso; I kinda expect a package named
'common'
On 04/28/2015 03:15 PM, Jan Chaloupka wrote:
Hi,
I have a package (kubernetes) which I would like to decompose into 2
subpackages A and B. Problem is A and B share some files and directories
so installing both of them on the same machine results in file
conflicts.
Another way of avoiding
Hi,
I have a package (kubernetes) which I would like to decompose into 2
subpackages A and B. Problem is A and B share some files and directories
so installing both of them on the same machine results in file
conflicts. Solution is to create the third package C, which provides all
those
On 04/28/2015 03:40 PM, Florian Festi wrote:
On 04/28/2015 03:15 PM, Jan Chaloupka wrote:
Hi,
I have a package (kubernetes) which I would like to decompose into 2
subpackages A and B. Problem is A and B share some files and directories
so installing both of them on the same machine results in
On 04/28/2015 03:40 PM, Florian Festi wrote:
On 04/28/2015 03:15 PM, Jan Chaloupka wrote:
Hi,
I have a package (kubernetes) which I would like to decompose into 2
subpackages A and B. Problem is A and B share some files and directories
so installing both of them on the same machine results in
