This release is a pre-release and may not be stable for production use.
make-home-links readme
Simplify your shell setup by making symlinks to your home folder.
It takes a TOML file and creates symlinks from your checkout.
Prerequisites
pipxor justpip3
Installation
One of:
pipx install make-home-linkspip install --user make-home-links
Upgrading:
pipx upgrade make-home-linkspip install --user -U make-home-links
After installation, make-home-links command should become available:
make-home-links --help
make-home-links --version
Development
The project uses hatch behind the scenes.
How to use
# reformat the code
make fmt
# run the cli
hatch run cli
# run the cli version
hatch run cli --version
# run the cli help
hatch run help
hatch run cli --help
# run mypy
hatch run types:check
# run tests
hatch run test
hatch run test -k usual_pytest_flags -m my_marker
# go to the dev shell
hatch shell
# build the distribution
hatch build
Increase version
hatch version <new_version>
Publishing
Test publishing
Create .env.test with contents (when doing first ever release, you will not be able to constrain the token to project -- create one for entire account and then switch to project-based token):
export HATCH_INDEX_USER=__token__
# token from "API tokens" of https://test.pypi.org/manage/account/
export HATCH_INDEX_AUTH=pypi-...
then publish to the testing PyPI:
hatch version <new_version>
source .env.test
hatch publish -r test -y
Publishing to prod
Create .env.prod with contents (when doing first ever release, you will not be able to constrain the token to project -- create one for entire account and then switch to project-based token):
export HATCH_INDEX_USER=__token__
# token from "API tokens" of https://pypi.org/manage/account/
export HATCH_INDEX_AUTH=pypi-...
then publish to the testing PyPI:
# maybe also: hatch version <new_version>
source .env.prod
hatch publish -r main -y
See also hatch publish documentation.
Metadata
Release files for make-home-links 0.1.0a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| make_home_links-0.1.0a1.tar.gz | 4.9 kB | Without provenance | Details for make_home_links-0.1.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| make_home_links-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details for make_home_links-0.1.0a1-py3-none-any.whl |
Total release size: 10.6 kB
Release files / make_home_links-0.1.0a1.tar.gz
| Download URL | make_home_links-0.1.0a1.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8bff9c496b277507db789ce770263b78929e07a76d2bb084e5d916271332bf9c
|
|
BLAKE2b-256 checksum How to use checksums |
8445f6b1f705a83a9d82cd13d985dbafa9a767f4c8f82e5dd870d48e36fe2b8e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.26.0
|
Release files / make_home_links-0.1.0a1-py3-none-any.whl
| Download URL | make_home_links-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ceffe5d0214b0f962a47308b6061981197961b1555b40aa6c922a79f23523e77
|
|
BLAKE2b-256 checksum How to use checksums |
232caddaad60b87e04cf2638245de20b3f0f3ace4ff114e182cae3506ceee34e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.26.0
|
Security for make-home-links 0.1.0a1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.