Open nbehrnd opened 2 years ago
This would be a helpful improvement, indeed. Unfortunately, I don't know how to do that.
Maybe somebody wants to contribute here? I've set the "help wanted" label.
@novoid By «git archeology» / reading the git log by June 2, 2020, I speculate Andrea Ghensi might help here. Because the symbolization / profile picture does not appear among the self declared «watchers» of this very project, I send one ping («one ping only ... ») to inform about the obstacle ahead.
@sanzoghenzo The selection of one Memacs module (e.g., about photos) currently yields the installation of all Memacs modules. Because the functionality was implemented by you, may you look on this again; perhaps it is just a detail you spot immediately to improve Memacs once again. Thank you!
Hi @nbehrnd , It's been a long time since I last used memacs, but this is what I got by a quick look:
pip install memacs[xxx]
where xxx is the functionality that you whish to have the dependencies installed;photos
: I once added the extras_requre
to setup.py
to define the dependencies of the modules that existed at that time, if new modules with external dependencies were created, they should have been added to the extras_require
dictionary.so, to fix this specific case:
"photos": ["Pillow"],
to the extras_require
dict in setup.py
pip install memacs[photos]
You will still see all the commands, but at least you only install the photos depencencies
I'll close this issue here as it seems to be a duplicate of #74
Feel free to continue discussing there.
After realizing the suggested change (see above and https://github.com/novoid/Memacs/issues/74#issuecomment-1186548950) I reopen this issue because it actually introduces an in-between step between the current situation (Memacs as one single big blob) and Memacs split up into separate repositories.
By being able to install the dependencies of selected modules, users are able to keep their setup footprint small in comparison to "setup every dependency at once".
The issue either suggests to reformulate the project's main
README.org
, or to revise how individual modules of Memacs are installed.The aim was to install Memacs with the photos module in an instance of Linux Debian 12/bookworm, branch testing. Before this, there was no permanent installation of Memacs at all (a virtual environment for Python earlier used for testing already was removed). At this point, there was no intent to use any other optional module of Memacs. This is why I thought
would fit well.
Contrasting to anticipation, the log reports the installation of multiple modules of Memacs:
for a total of
though for now I would like to get familiar with a sub set of them.