greatly reduced set of dependencies but with grown size).
>
> This is - hopefully - the long-term goal, because upstream is
> slowly thinking about building qemu-system as a single binary
> which provides emulation of everything available, - obviously
> we won't try to split such binary into multiple packages :)
> But this goal seems to be too far in the future to be plannable.
>
> Without such merge into single binary, the package will be large
> (see full list of emulator binaries above), but hdd space is
> much cheaper nowadays..
>
> What do you think?
>
> /mjt
--
Christian Ehrhardt
Senior Staff Engineer, Ubuntu Server
Canonical Ltd
online.
>>
>> Thanks,
>>
>> --
>> Sergio
>> GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
>> Please send encrypted e-mail if possible
>> https://sergiodj.net/
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
of my builds failing to this
commit [1] that has to land into debhelper to resolve it.
[1]: https://salsa.debian.org/debian/debhelper/-/commit/d70caa69c64b
> So, which one of these paths should be used and why?
> - /lib/systemd/system/
> - /usr/lib/systemd/system/
>
> Thanks!
&g
Subject: ITP: dpdk -- Data Plane Development Kit
Package: wnpp
Owner: Christian Ehrhardt
Severity: wishlist
* Package name: dpdk
Version : 2.2
Upstream Author : Thomas Monjalon
* URL : http://dpdk.org/
* License : BSD (core libs), GPLv2 (kernel components
4 matches
Mail list logo