Re: pkg_dry on DragonFlyBSD

[Hasso Tepper <hasso@xxxxxxxxx>]

Steve O'Hara-Smith wrote:
> Like kqemu it's a kernel module with only one client, kqemu is only
> used by qemu and the DRM kernel module is only used by the Xorg server.
> They are both bridge modules with one end of their interfaces
> determined by the client (and thus not under the control of the
> DragonFly project) and one end determined by the kernel interfaces of
> DragonFly. Both of these interfaces are subject to change over time.

There is many things not under control of the DragonFly project.

> There may well come a time for either of these where there are two
> incompatible versions extant supporting two actively used versions of
> their client (think around a major version bump).

This situation just isn't acceptable. It isn't acceptable even for Linux 
(as DRM "upstream").

> It would be much easier to maintain multiple active versions in the 
> pkgsrc framework than in the kernel source tree.

Have you tried it? How do you manage kernel interface changes? It isn't 
hypothetical, DRM depends closely on many things in kernel (agp(4), 
pci(4)). How do you manage having pkgsrc package files outside of pkgsrc 
prefix?


-- 
Hasso Tepper