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

Package libqfieldsync as wheel #526

Merged
merged 11 commits into from
Nov 19, 2023
Merged

Package libqfieldsync as wheel #526

merged 11 commits into from
Nov 19, 2023

Conversation

m-kuhn
Copy link
Member

@m-kuhn m-kuhn commented Jun 17, 2023

Depends on

Developer information, to work locally, either install the requirements.txt (if you don't need to edit libqfieldsync) or pip install libqfieldsync as editable if you need to work on libqfieldsync.

git clone [email protected]:opengisch/libqfieldsync.git
pip install -e libqfieldsync

@@ -4,3 +4,6 @@ flake8-respect-noqa
pytest
future
transifex-client

# TODO: point to a commit on master after merging https://github.com/opengisch/libqfieldsync/pull/49
Copy link
Member Author

Choose a reason for hiding this comment

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

Open todo ...

@m-kuhn m-kuhn force-pushed the libqfieldsyncwheel branch 2 times, most recently from ab1472f to 88f7404 Compare June 19, 2023 06:33
@m-kuhn
Copy link
Member Author

m-kuhn commented Oct 3, 2023

@suricactus this should be ready.
One TODO: point to a commit on master after merging the PR on opengisch/libqfieldsync#49

@suricactus suricactus merged commit 512e162 into master Nov 19, 2023
7 checks passed
@suricactus suricactus deleted the libqfieldsyncwheel branch November 19, 2023 03:22
@m-kuhn
Copy link
Member Author

m-kuhn commented Nov 19, 2023

I think we will want to points to a sha on master and update explicitly

@suricactus
Copy link
Collaborator

Yes, we want that for releases, I do have it mind. Will pinpoint when I am about to release a new version, there is a bit of other development to be made for now.

Also thinking whether to create a release branch as I did on QFieldCloud and pinpoint only there, so we are forced to keep libqfieldsync and qfieldsync master branches compatible with each other, until we think it's not working.

suricactus added a commit that referenced this pull request Nov 20, 2023
Seems what has been described in #526 was never shared in the docs.
suricactus added a commit that referenced this pull request Nov 21, 2023
Seems what has been described in #526 was never shared in the docs.
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