On Fri, Feb 20, 2015 at 06:12:11PM +0100, Jaromil wrote:
>
> dear Isaac,
>
> On Fri, 20 Feb 2015, Isaac Dunham wrote:
>
> > On Sun, Feb 15, 2015 at 04:27:55PM +0000, Luke Kenneth Casson Leighton wrote:
> > > http://lkcl.net/reports/removing_systemd_from_debian/
> >
> > Somehow, this inspired me to poke at packaging mdev.
> > I don't have a website or apt repository atm, so I can't provide a deb.
> > But here's the source in git:
> >
> > https://github.com/idunham/mdev
> >
> > To build it, use "dpkg-buildpackage -b".
>
> if you like to use our CI system and apt repository, you are welcome.
>
> we can open an mdev project on our gitlab inside a new group for the
> sort of projects like vdev and mdev, something called packages-nextgen,
> there you'd be able to push mdev as a mirror in addition to your github
>
> the advantages for this would be multiple: you'd have continuous
> integration on mdev and the correctly built packages would be ready to
> use from the Devuan repository, making it much easier for people to test
> and give you feedback.

Thank you very much. That sounds nice.
I'm curious whether this works nicely with debian-source-native
packaging, like I'm using for mdev (everything including the packaging
and source is in git master).

I suppose I should also package libsysdev, since Jude was talking
about using it for parts of libudev-compat.

If you're wondering why I didn't respond sooner: lkcl and I were chasing
down a bug, which turned out to be breakage with initramfs-tools from
wheezy.
I also didn't want the mdev package to be something that someone *could*
install easily at that stage, since the only other person to try it got
a boot failure; at a certain point, someone who isn't ready to build
the package probably isn't ready to help test it.

But now that lkcl has figured out how to fix the bug, I suppose it's ready
for putting into an experimental repository.

Thanks,
Isaac Dunham