> Maybe the *.nfo files should be extended by listing optional
> dependencies, so we could handle these an automated way?
NO
REQUIRES in .info should only be used for mandatory dependencies, not
optional dependencies.
> Another subject are dependencies required only during build-time
> vss depend
> Hi everybody !
>
> findpkg is on version 20160817 both on the file to download in
> findpkg.info and on the SlackBuild script, but the VERSION in the findpkg.info
> file is still 20160710.
>
> It could confuse some auto-build scripts...
Fixed in my branch
Thanks
--
Willy Sudiar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/19/2016 06:22 PM, Sebastian Arcus wrote:
> On 19/10/16 21:26, Nishant Limbachia wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> On 10/19/2016 08:41 AM, Franzen wrote:
>>> On 19.10.2016 12:17, Sebastian Arcus wrote:
O
On 10/20/2016 01:23 AM, King Beowulf wrote:
> Usbredir is not a "hard" dependency that prevents qemu from compiling.
> Rather, it is an optional dependency to add functionality. This is
> mentioned in the README.
I'm aware, but without usbredir virt-manager becomes kind
of unusable. I remember o
On 10/19/2016 03:26 PM, Thomas Szteliga wrote:
> Hello,
>
> shouldn't usbredir be listed in REQUIRES of QEMU and spice-gtk?
>
> Because when QEMU is compiled without usbredir present
> (autodetected during compilation) virt-install usage will
> be problematic or even impossible.
>
>
---
Usbred
On 19/10/16 21:26, Nishant Limbachia wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/19/2016 08:41 AM, Franzen wrote:
On 19.10.2016 12:17, Sebastian Arcus wrote:
On 19/10/16 10:59, Franzen wrote:
On 19.10.2016 11:42, Sebastian Arcus wrote:
The clamav-unofficial-sigs.cron crond
Hello,
shouldn't usbredir be listed in REQUIRES of QEMU and spice-gtk?
Because when QEMU is compiled without usbredir present
(autodetected during compilation) virt-install usage will
be problematic or even impossible.
This won't work without usbredir:
# virt-install \
--connect qemu://
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/19/2016 08:41 AM, Franzen wrote:
> On 19.10.2016 12:17, Sebastian Arcus wrote:
>> On 19/10/16 10:59, Franzen wrote:
>>> On 19.10.2016 11:42, Sebastian Arcus wrote:
The clamav-unofficial-sigs.cron crond crontab file included with
clam
On 19.10.2016 12:17, Sebastian Arcus wrote:
On 19/10/16 10:59, Franzen wrote:
On 19.10.2016 11:42, Sebastian Arcus wrote:
The clamav-unofficial-sigs.cron crond crontab file included with
clamav-unofficial-sigs seems to be incompatible with the version of Cron
used on Slackware. It uses the extr
On 19/10/16 10:59, Franzen wrote:
On 19.10.2016 11:42, Sebastian Arcus wrote:
The clamav-unofficial-sigs.cron crond crontab file included with
clamav-unofficial-sigs seems to be incompatible with the version of Cron
used on Slackware. It uses the extra field for the username (clamav)
which seems
On 19.10.2016 11:42, Sebastian Arcus wrote:
The clamav-unofficial-sigs.cron crond crontab file included with
clamav-unofficial-sigs seems to be incompatible with the version of Cron
used on Slackware. It uses the extra field for the username (clamav)
which seems to break things on Slackware. I've
The clamav-unofficial-sigs.cron crond crontab file included with
clamav-unofficial-sigs seems to be incompatible with the version of Cron
used on Slackware. It uses the extra field for the username (clamav)
which seems to break things on Slackware. I've just noticed this on
several clamav insta
12 matches
Mail list logo
