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

Add installCommand to ypkg-install-deps invocation #117

Merged
merged 1 commit into from
Oct 23, 2024

Conversation

ermo
Copy link
Contributor

@ermo ermo commented Oct 16, 2024

This ensures that ypkg uses either the default installCommand or the one that was passed in as an argument.

This ensures that ypkg uses either the default installCommand or the one
that was passed in as an argument.

Signed-off-by: Rune Morling <[email protected]>
@ermo
Copy link
Contributor Author

ermo commented Oct 23, 2024

Has been tested by staff via getsolus/packages#3850 and getsolus/packages#4063 for a week now.

@ermo ermo marked this pull request as ready for review October 23, 2024 15:51
@ermo ermo requested review from joebonrichie and silkeh October 23, 2024 15:52
Copy link
Member

@silkeh silkeh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@ermo ermo merged commit 3ec7d86 into master Oct 23, 2024
1 check passed
ermo added a commit to getsolus/packages that referenced this pull request Nov 4, 2024
**Summary**

- `eopkg.py2` now writes versioned (v3), gdbm format FilesDB shelves,
and versioned LazyDB caches; both using Pickle Protocol Version 2.
- `eopkg.py3/bin` now writes versioned (v4), gdbm format FilesDB
shelves, and versioned LazyDB caches; both using Pickle Protocol Version
2.
- FilesDB and LazyDBs are autoupgraded on version mismatch.
- The output of `sudo eopkg.py2/py3/bin rdb` operations has been cleaned
up significantly.
- Taskfile now uses `eopkg.bin` for indexing operations due to the
improved output it provides.
- ypkg-install-deps supports an optional -e/--eopkg-cmd argument, which
defaults to `eopkg.py3`
(look at getsolus/solbuild#117 for how this will
be leveraged in solbuild).

This is intended to help make the transition between using `eopkg.py2`
and `eopkg.py3/bin` much smoother.

**Changelog**

- [eopkg.py2
3.12.5](https://github.com/getsolus/eopkg/releases/tag/v3.12.5)
- [eopkg.py3
4.1.5](https://github.com/getsolus/eopkg/releases/tag/v4.1.5)
- [eopkg.py3
4.1.6](https://github.com/getsolus/eopkg/releases/tag/v4.1.6)

**Test Plan**

- Check out this branch
- Clean out the local repo with `go-task clean-local`
- Build pisi w/ `go-task localcp` and install it
- Pay attention to any mentions of FilesDB rebuilds in subsequent build
logs (e.g. eopkg, ypkg and whatever else you decide to build for testing
purposes). In particular, pay attention to the `FilesDB (version:` part.
- Build eopkg w/ `go-task localcp` and install it and its `python-eopkg`
subpackage
- Notice how after installing the updated eopkg, subsequent builds will
now show a list of which packages are indexed in the local repo prior to
the build.
- Build ypkg w/ `go-task localcp` and install it
- Follow the Test Plan in #3850 

**Checklist**

- [x] Package was built and tested against unstable
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