Git Product home page Git Product logo

Comments (21)

ddurieux avatar ddurieux commented on July 17, 2024

We don't have decided to add packaging files (deb, rpm, bsd...) in an other repository?

from alignak.

Seb-Solon avatar Seb-Solon commented on July 17, 2024

Branch / repo is basically the same (not with the code)

from alignak.

titilambert avatar titilambert commented on July 17, 2024

in this case, branch means detached branch ... a new repo could be easier ?
In this repo/branch, there will be: files and folder used for packaging (spec files, debian, ...)
And a tarball of Alignak master.
What do you think ?

from alignak.

Seb-Solon avatar Seb-Solon commented on July 17, 2024

Yeah a repo packaging with branch debian / rpm could be great no?

from alignak.

ddurieux avatar ddurieux commented on July 17, 2024

A branch or a folder for each packaging system (prefer folder because it's more easier to read)

from alignak.

gst avatar gst commented on July 17, 2024

Sorry but don't remember too the talks we had about this..

and sorry twice but I dislike the idea to create yet another repository for this, why not have a folder named 'packaging' in our top and in it have subfolders : debian, fedora, redhat, ubuntu (no this is mean for real distribution) and so on ..

were there some cons about this possibility ?

from alignak.

hvad avatar hvad commented on July 17, 2024

Hi,

I begin work to make rpm for fedora/epel and i think we just need source for that work correctly ;-).

You can make debian directory on that repository and create a spec file for fedora/epel.

But the main jobs is to work with systemd ^^.

See you soon on irc

from alignak.

gst avatar gst commented on July 17, 2024

related: #180

from alignak.

titilambert avatar titilambert commented on July 17, 2024

The packaging is already done on surveil project... see here: https://github.com/surveil/surveil-packaging/blob/centos/alignak/alignak.spec

from alignak.

Seb-Solon avatar Seb-Solon commented on July 17, 2024

First spec draft done on alignak-packaging.

Links to help : https://fedoraproject.org/wiki/How_to_create_an_RPM_package, https://fedoraproject.org/wiki/Packaging:RPMMacros

Macro list are very useful when you look for a specific file.

from alignak.

hvad avatar hvad commented on July 17, 2024

Hi,

i known because i use everyday ^^. See ->
http://paste.fedoraproject.org/269102/17308144

Bye

2015-09-18 22:37 GMT+02:00 Sébastien Coavoux [email protected]:

First spec draft done on alignak-packaging.

Links to help :
https://fedoraproject.org/wiki/How_to_create_an_RPM_package,
https://fedoraproject.org/wiki/Packaging:RPMMacros

Macro list are very useful when you look for a specific file.


Reply to this email directly or view it on GitHub
#174 (comment)
.

David Hannequin

from alignak.

hvad avatar hvad commented on July 17, 2024

See https://fedoraproject.org/wiki/Packaging:Python

from alignak.

Seb-Solon avatar Seb-Solon commented on July 17, 2024

Ok first working file is done. We have to agree on some points :

  • Package structure : I'm for one alignak-common and one alignak-doc packages. We could split by daemon but it's not really worth it and I'm afraid of conflicts. Two package will provide the same files (python files)
  • Install path for python binaries : In the draft it's /usr/bin, we could argue on /usr/sbin
  • Requirements : I'm not sure for python-imporlib. Maybe we will need some if to add it to requirement. I'm afraid recent (f22) distro will fail because the package is not installed but it's now in standard python lib
  • Init script / systemd : Another if to do? The draft copy /etc/init.d/alignak* shell scripts and /etc/default/alignak files
  • .pth file : I'm not 100% sure this is needed, I removed it in packaging

See Alignak-monitoring/alignak-packaging@806f976 and https://github.com/Alignak-monitoring/alignak-packaging/blob/master/alignak.spec . I'm not sure if I will PR on "rpm" or "fXX" branch because I'm afraid we will need several spec.

from alignak.

aviau avatar aviau commented on July 17, 2024

Init script / systemd : Another if to do?

I don't know for Fedora, but in Debian we ship both the sysvinit and systemd files. So that shouldn't be an if.

we could argue on /usr/sbin

Absolutely

I'm for one alignak-common and one alignak-doc packages

I agree.

from alignak.

hvad avatar hvad commented on July 17, 2024

Hi, my point of view :

Package structure : I'm for one alignak-common and one alignak-doc packages. We could split by daemon but it's not really worth it and I'm afraid of conflicts. Two package will provide the same files (python files)

Yes, alignak-common is good idea but i not sure for doc.

Install path for python binaries : In the draft it's /usr/bin, we could argue on /usr/sbin

It's more an habit than a rule.

Requirements : I'm not sure for python-imporlib. Maybe we will need some if to add it to requirement. I'm afraid recent (f22) distro will fail because the package is not installed but it's now in standard python lib

I think it's on standard python lib until centos 7 and fedora 20.

Init script / systemd : Another if to do? The draft copy /etc/init.d/alignak* shell scripts and /etc/default/alignak files

I prefer systemd script rule and i think we must forget sysV for Linux.

.pth file : I'm not 100% sure this is needed, I removed it in packaging

Yes

from alignak.

Seb-Solon avatar Seb-Solon commented on July 17, 2024

I forgot one last thing :
The setup generate .pyc and .pyo. Fedora pacaking suggest to keep them but maybe both file for each python file is a bit overkill. I don't think wee need a .pyc and a .pyo file for a specific file. I need to look documentation/usage. If you have opinion/idea about this feel free to help me.

from alignak.

gst avatar gst commented on July 17, 2024

The setup generate .pyc and .pyo. Fedora pacaking suggest to keep them but maybe both file for each python file is a bit overkill. I don't think wee need a .pyc and a .pyo file for a specific file.

*pyc are the (pre-)compiled source files.
and *pyo are same than *pyc but for "optimized" python calls (python -O some_script.py, which actually only remove/delete the assert from the sources).

I think it's better/simpler to keep both ; that doesn't hurt at all (some kbytes used, that's all)..

why would you bother remove them, they would be anyway rebuild/regenerated where the package would be executed the first time.. normally, because if, for instance, the file system where the source is located/installed is readonly then this wouldn't be possible. I think that's exactly the goal of the pre-compile during package build : have the *pyc & *pyo (directly) available (even if readonly filesystem so) on the installed destination..

from alignak.

Seb-Solon avatar Seb-Solon commented on July 17, 2024

Debian packaging is working. Waiting for review of @titilambert

from alignak.

mohierf avatar mohierf commented on July 17, 2024

What about this @Seb-Solon @titilambert @ddurieux @hvad

from alignak.

mohierf avatar mohierf commented on July 17, 2024

@Seb-Solon ? What about this now ?

from alignak.

Seb-Solon avatar Seb-Solon commented on July 17, 2024

See https://github.com/Alignak-monitoring/alignak-packaging for all packaging related stuff

from alignak.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.