]] Russ Allbery > 2. Package logind separately from systemd, get it working with sysvinit. > The problems with doing this, as I understand it, is that we'd not be > able to upgrade such a separately-packaged logind beyond 204 for > jessie. I'm not sure how much impact that would have. Also, it > sounded to me like we would need to figure out who was going to do that > work and maintain that package, including in the stable release. If > the current systemd maintainers are not interested in doing this, we > absolutely shouldn't try to force them to do so. Someone else would > need to step forward to do this and figure out the right package > relationships. (Also, it would be good to maintain this separately so > that the systemd maintainers could move forward with newer versions of > systemd, including the logind built from its source.)
[...] > The systemd maintainers should definitely feel free to tell me if I'm > misunderstanding their feelings on option 2. You are not. I'd like to expand slightly that I'd be ok with having it part of the systemd package as long as somebody shows up and commits to maintaining that functionality long-term and with the explicit understanding of the TC that if the necessary manpower to do that work disappears we will not be holding to rest of the init system back. It might be that packaging up logind completely separately by such a person (or team) might be a better approach (as you suggest). -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
