On ven., 2016-02-19 at 17:47 +0100, Maxime Gauduin wrote:
> On Fri, Feb 19, 2016 at 4:12 PM, Sébastien Luttringer
> wrote:
>
> > I didn't tried them but I don't get how this can works when you
> > install/update
> > a dkms module.
> >
> I'm aware of that, they were designed that way. That's why
On Fri, Feb 19, 2016 at 4:12 PM, Sébastien Luttringer
wrote:
> On ven., 2016-02-19 at 08:12 +0100, Maxime Gauduin wrote:
> > On Fri, Feb 19, 2016 at 2:27 AM, Sébastien Luttringer
> > wrote:
> > What about when you remove a dkms package? Would be nice to remove the
> > build modules as well.
> Th
On ven., 2016-02-19 at 08:12 +0100, Maxime Gauduin wrote:
> On Fri, Feb 19, 2016 at 2:27 AM, Sébastien Luttringer
> wrote:
> What about when you remove a dkms package? Would be nice to remove the
> build modules as well.
This is done by post install scriplet[1] of each dkms module package (e.g it
On Fri, Feb 19, 2016 at 2:27 AM, Sébastien Luttringer
wrote:
> Hello,
>
> I pushed into community-testing a new version of dkms, with an alpm hook to
> build oot modules at install time, instead of at startup time with the
> systemd
> service.
>
> The hooks is very simple; it build and install dk
Hello,
I pushed into community-testing a new version of dkms, with an alpm hook to
build oot modules at install time, instead of at startup time with the systemd
service.
The hooks is very simple; it build and install dkms registered modules for all
installed kernel version when a package ending
5 matches
Mail list logo