Thanks for the tips on this. I am brand new to packaging Debian products. The
product I am working on packaging is
https://github.com/keepassxreboot/keepassxc. My main goal with packaging it is
because I am a big fan of it and I keep my systems clean so I want a pure
Debian package that I can i
On 02/26/2017 04:52 PM, The Wanderer wrote:
> On 2017-02-26 at 10:47, Ghislain Vaillant wrote:
>
>> On Sun, 2017-02-26 at 10:15 -0500, matt jones wrote:
>>
>>> I am packaging a gui that has dependencies for qt and such. How do
>>> I go about ensuring that X is available as well? Do I list that as
On 2017-02-26 at 10:47, Ghislain Vaillant wrote:
> On Sun, 2017-02-26 at 10:15 -0500, matt jones wrote:
>
>> I am packaging a gui that has dependencies for qt and such. How do
>> I go about ensuring that X is available as well? Do I list that as
>> a dependency as well. The upstream maintainers d
On Sun, 2017-02-26 at 10:15 -0500, matt jones wrote:
> I am packaging a gui that has dependencies for qt and such. How do I go about
> ensuring that X is available as well? Do I list that as a dependency as well.
> The upstream maintainers don’t call it out specifically but it is understood.
> L
Dear Matt,
libqt5gui5 is already depending on the needed X libraries, so unless
your app is doing something tricky, you don't need to care about this.
But we can tell more if we see the application in question...
Regards,
Zoltan Gyarmati
https://zgyarmati.de
On 02/26/2017 04:15 PM, matt jones
Dear Matt,
libqt5gui5 is already depending on the needed X libraries, so unless
your app is doing something tricky, you don't need to care about this.
But we can tell more if we see the application in question...
Regards,
Zoltan Gyarmati
https://zgyarmati.de
On 02/26/2017 04:15 PM, matt jones
6 matches
Mail list logo
