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

Make core and trails installable #6298

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

jayvdb
Copy link

@jayvdb jayvdb commented Jan 23, 2020

Implements #6297

@stamparm
Copy link
Owner

Thank you for your work, though, you've oversimplified this one:

A) core is not the Maltrail. core is only holding the core functions required by the both sensors and server
B) thirdparty is usable for (e.g.) users using git method (currently all of users). I don't see a problem of it staying there as is because those same libraries are not versatile in updates nor features
C) There is a bigger issue here, which is not related to the PyPI structuring and that is the installation of Maltrail as a service on generic *nix systems. Just pip install maltrail won't do much in current state

@jayvdb
Copy link
Author

jayvdb commented Jan 23, 2020

The intent isnt for this to be final, nor for pip install maltrail to become a solution for installation of maltrail. Both are possible, but would be more disruptive to the current codebase, and would be a wasted effort to do unless you are interested in publishing to PyPI, and providing support for installation from PyPI, which may not be appropriate at the moment.

The objective is solely to make some of the maltrail functionality available to other applications, as described at #6297 . I would use this immediately, and I suspect others would also, and with more app developers relying on maltrail, hopefully that results in more people helping with maintaining it also.

If you do want sensors and server included in the PyPI package, I can do that also. Then the PyPI sdist would be approaching what distro packagers could be able to consume, and of course they would add the service files needed.

Including thirdparty in a PyPI package is possible too, and such vendoring is not uncommon, especially of six. I can do that also, and in my distro packaging I then just patch to the source to de-vendor these.

@jayvdb
Copy link
Author

jayvdb commented Jan 31, 2020

@stamparm , could you please give me more direction on how to proceed. I would really like to use maltrail's features as part of a library I am building without resorting to copying&pasting them.

@stamparm
Copy link
Owner

@jayvdb as far as I can see, you are interested ONLY into trails, because bundling ONLY the core doesn't make any sense. There is no point in making maltrail PyPI package which will hold only trails inside (along with dummy core). Hence, I'll need to drop this until I do it properly (for all the functionality)

@jayvdb
Copy link
Author

jayvdb commented Feb 1, 2020

I am also using a few parts of core, which is why I included it.

As indicated above, I am happy to do a more complete version if that is what you want, and your last post indicates that, so I will do that today.

@stamparm
Copy link
Owner

stamparm commented Feb 3, 2020

@jayvdb please, I'll do this when I catch time. I just need to think about it to do it properly

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

Successfully merging this pull request may close these issues.

2 participants