I expect the init scripts to be fairly static and not change often and they're
simple. Any effort spent for engineering a solution to avoid duplicate init
scripts seems a waste of time to me. Can we go with separate copies for now and
address it later should it become a maintenance issue?
--
Moved the redhat sysv init scripts and updated setup.py accordingly.
--
https://code.launchpad.net/~juergh/cloud-init/add-debian-init-scripts/+merge/174943
Your team cloud init development team is requested to review the proposed merge
of lp:~juergh/cloud-init/add-debian-init-scripts into
Juerg,
As for the last comment (sysvinit/something)
mkdir sysvinit/redhat
bzr add sysvinit/redhat
bzr mv sysvinit/cloud-* sysvinit/redhat
You'll also have to modify setup.py to make INITSYS_FILES['sysvinit'] read from
sysvinit/redhat/*
and then also to use sysvinit/debian/* for
Juerg Haefliger has proposed merging
lp:~juergh/cloud-init/add-debian-init-scripts into lp:cloud-init.
Requested reviews:
cloud init development team (cloud-init-dev)
For more details, see:
https://code.launchpad.net/~juergh/cloud-init/add-debian-init-scripts/+merge/174943
This merge request
Juerg,
I am interested in having sysvinit scripts on debian in trunk, so thanks for
your work here.
The thing that I'm not so interested in is maintaining two sets of sysvinit
scripts that really are the same.
Just glancing, it seems that the ones ins sysvinit are largely more complete
5 matches
Mail list logo
