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

Ongoing Development #15

Open
8 of 22 tasks
rnixx opened this issue May 5, 2023 · 3 comments
Open
8 of 22 tasks

Ongoing Development #15

rnixx opened this issue May 5, 2023 · 3 comments

Comments

@rnixx
Copy link
Member

rnixx commented May 5, 2023

  • Extend topics/domains:
    • Create ruff domain in qa topic
    • Create webpack domain in js topic
    • Create jest domain in js topic
    • Create yarn domain in js topic
    • Create nvm domain in js topic
  • Implement custom template generation configured via mx.ini
  • Complete docs
  • Add help targets
  • Support some kind of "proxy" targets. They should use the environment of the main package and call make in sources/[package] if configured in mx.ini
  • Support update flag in mxmake command, updating the Makefile without prompting for settings
  • Support "preseeds" for running mxmake init
  • Support useful basic mx.ini file configuration when running mxmake init
  • Environment path improvements. Modify PATH instead of working with MXENV
  • Support usage of uv (https://github.com/astral-sh/uv) as substitute for pip and for creating virtual environments PR uv runs on mxmmake #25
  • Try if mxmake works on windows when using git bash try to run with git-bash on windows #29
  • Replace topics.py deprecated use from pkg_resources import iter_entry_points with importlib https://docs.python.org/3/library/importlib.metadata.html#entry-points PR use importlib.metadata to load entrypoints #28
  • enhance to not depend only on root Makefile but also on includes.
  • core.sources depends on core.files
  • adding core.sources to an existing Makefile breaks unless make clean called
  • OS environment variable is available only on windows. The way it is used causes problems with sub make calls on linux. https://stackoverflow.com/questions/714100/os-detecting-makefile
  • remove wtr coverage directory on make clean
@rnixx
Copy link
Member Author

rnixx commented Feb 26, 2024

Although PATH handling is already implemented, I'm not entirely happy with the solution.

I want to try removing .ONESHELL and invoking the shell as follows:

SHELL=env PATH=$(if $(EXTRA_PATH),"$(EXTRA_PATH):","")$(PATH) bash

If this or something similar works as expected we can avoid exporting PATH at multiple places.

See https://stackoverflow.com/a/36226832

@jensens
Copy link
Member

jensens commented Mar 4, 2024

Although PATH handling is already implemented, I'm not entirely happy with the solution.

I want to try removing .ONESHELL and invoking the shell as follows:

SHELL=env PATH=$(if $(EXTRA_PATH),"$(EXTRA_PATH):","")$(PATH) bash

If this or something similar works as expected we can avoid exporting PATH at multiple places.

See https://stackoverflow.com/a/36226832

AFAIK you talked to Richard and conclusio was this is not necessary right?

@rnixx
Copy link
Member Author

rnixx commented Mar 4, 2024

@jensens right, this comment is obsolete

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