setuptools support

[linxon]

Hi!
do you can add the setuptools support?

[j3ssie]

Yeah of course but I have some other features on TODO list for now.

[linxon]

thank you! ^_^

also it would be great if this project could support XDG Base Directory Specification

P.S.

[+] Make new directory: /tmp/linxon-tmp-files/workspaces/linxon.ru
 * Serving Flask app "app" (lazy loading)
 * Environment: production
   WARNING: Do not use the development server in a production environment.
   Use a production WSGI server instead.
 * Debug mode: on
/usr/lib64/python3.6/site-packages/osmedeus/core/rest
[+] Writing /usr/lib64/python3.6/site-packages/osmedeus/core/rest/storages/options.json
[-] Writing fail: /usr/lib64/python3.6/site-packages/osmedeus/core/rest/storages/options.json
[*] Cleasning activities log
[+] Writing /usr/lib64/python3.6/site-packages/osmedeus/core/rest/storages/activities.json
[-] Writing fail: /usr/lib64/python3.6/site-packages/osmedeus/core/rest/storages/activities.json
---<---<--@ Target: linxon.ru @-->--->---

[j3ssie]

That's will help reduce verbose log but the purpose of that is the plugin tool or workspace can be located from anywhere in the machine.

[blshkv]

just to make it clear, it is NOT enough just to create a single setup.py file. You need to rewrite the code so it won't be changing a system-installed software (these json files, may be others) and redirect all output to a local (userdir ./~xxx) folder.

[j3ssie]

Look like you guys built it for me so I'm gonna close this issue.
Thank you very much!

[blshkv]

No, it is not fixed

[blshkv]

ping?.. Can you point it out how it was fixed? There is no setup.py and it were no relevant commitments.

[j3ssie]

I thought @linxon create some commits for it.

[nqb]

@j3ssie, I supposed you would like to say @linxon in place of @nqb ;-)

[j3ssie]

@j3ssie, I supposed you would like to say @linxon in place of @nqb ;-)

Sorry, my fat fingers -_-

[blshkv]

so we installed it as a module eventually using workarounds.
But it would be much easier for everyone if you would create a proper setup.py.

[blshkv]

laramies/theHarvester#52 if you want to know more or look at examples.. There is a pull request over where we changed the structure and came up with a proper setup.py

[j3ssie]

The issue is no longer exist due to the repo having been upgraded to Osmedeus Next Generation v4.0

[blshkv]

What you have done with osmedeus-base is ridiculous. People in the right mind should never trust and run
curl -fsSL https://.../install.sh. In addition to the trust issue, that script runs some commands like pip with sudo somemore which is WILL screw up Gentoo's installation for sure (as an example).

Please fix THIS issue, we will continue packaging it as it should be.

[blshkv]

I have added osmedeus to our hall of shame for now,
see pentoo/pentoo-overlay#596