Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move packaging stuff to the packaging repo #655

Closed
4 tasks
mohierf opened this issue Dec 20, 2016 · 4 comments
Closed
4 tasks

Move packaging stuff to the packaging repo #655

mohierf opened this issue Dec 20, 2016 · 4 comments
Assignees

Comments

@mohierf
Copy link
Contributor

mohierf commented Dec 20, 2016

Jointly with this alignak packaging issue, some modifications may occur in the alignak main repo:

  • the bin directory contains startup scripts for Debian/Ubuntu SysV (*init.d) and for FreeBSD (rc.d), we should move this to the alignak-packaging repo which already contains the systemd scripts

  • the bin directory contains a default/alignak.in file used by the init.d scripts. This file is intended to become the main entry point for Alignak installation (as explained in this issue). As such, we may move this file to another folder and provide a default version for the packagers.
    [edit] Instead of re-using the alignak.in file used by the init.d scripts we may have another dedicated file with a standard format compatible with any OS. To be tested with an ini file format...

  • the distutils python setup.py script must be updated according to those new rules

  • the dev directory contains some script that are intended to be used by the developers to start / stop alignak. We must promote using those scripts rather than the bin/init.d scripts when alignak is used from the git repository

@mohierf mohierf self-assigned this Dec 20, 2016
@mohierf
Copy link
Contributor Author

mohierf commented Dec 20, 2016

@ddurieux @Seb-Solon : what do you think about this proposal? Having all the packaging stuff in the alignak packaging repo seems legit to me.

I do not understand why it was necessary to have a dedicated repo for the packaging, and I did not found an explanation of this choice, but it exists... and, as such having init.d / rc.d scripts in the alignak repo is a non-sense that may lead people to misunderstanding as it did for me 😉


[*edit]: after discussing with @hvad it seems that the easiest solution for the packaging should be to have the manpages and the system scripts in the main project repo. @ddurieux @Seb-Solon : what should we decide for Alignak?

@mohierf
Copy link
Contributor Author

mohierf commented Dec 20, 2016

@algorys: As of #649, you should consider the 4th item in my comment. We should promote using the dev folder scripts to run alignak when one cloned the repository instead of using the init.d scripts that are intended to be used as system start scripts for a system V Debian installation.

The alignak tutorial should take this into consideration also ... it would be really better. I am having a look at those scripts to confirm they are fully functionnal 😉

mohierf added a commit to Alignak-monitoring/alignak-packaging that referenced this issue Dec 20, 2016
mohierf added a commit to Alignak-monitoring/alignak-packaging that referenced this issue Dec 20, 2016
@ddurieux
Copy link
Contributor

From my memory, we had split because the tagging of packages will be not synchronized with alignak release management

@mohierf
Copy link
Contributor Author

mohierf commented Dec 21, 2016

Closing to favor #656

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants