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

Include libxdo.pc in release tarball #345

Merged
merged 2 commits into from
Aug 4, 2021
Merged

Include libxdo.pc in release tarball #345

merged 2 commits into from
Aug 4, 2021

Conversation

foutrelis
Copy link
Contributor

make install fails when trying to package v3.20210804.1 because pc.sh is missing.

I opted to generate and include libxdo.pc directly instead of shipping pc.sh in the tarball.

Also drop the "|| true" from the "rm -f" command as likely unneeded.
@jordansissel jordansissel merged commit dd985f5 into jordansissel:master Aug 4, 2021
@jordansissel
Copy link
Owner

Thanks for the quick fix :)

@foutrelis foutrelis deleted the include-libxdo.pc-in-release-tarball branch August 4, 2021 16:24
@foutrelis
Copy link
Contributor Author

Hmm, do you know what's up with the tags? v3.20210804.2 points to a commit that's not on any branch and 3.20210804.2 is not an actual release with accompanying tarball. Thanks for doing new releases btw, I use xdotool daily (for simple tasks generally).

(Sorry for nitpicking. 🐱)

@foutrelis
Copy link
Contributor Author

Correction: The .2 release has the wrong version in libxdo.pc only; `xdotool -v' shows the correct version. Probably not worth bothering with a new release just for the version string in libxdo.pc. :)

@jordansissel
Copy link
Owner

jordansissel commented Aug 4, 2021 via email

@foutrelis
Copy link
Contributor Author

To guard against this, the update-version target could be made to regenerate libxdo.pc or you could ship pc.sh in the tarball (and exclude libxdo.pc). Not sure which solution is preferable though (leaning towards keeping libxdo.pc in the tarball).

The two tags for .2 are a bit confusing; don't know if this is fixable (or even worth fixing). Seems the one with the v prefix points to a commit that updated CHANGELIST but is not on the master branch. The 3.20210804.2 tag (without the v in front) is missing the CHANGELIST update but has the version bump and appears to be the origin of the xdotool-3.20210804.2.tar.gz tarball (which however is attached to the v3.20210804.2 tag/release)..

buldi pushed a commit to buldi/xdotool that referenced this pull request Apr 23, 2022
* Add libxdo.pc and README.md to release tarball

* Add libxdo.pc to clean target

Also drop the "|| true" from the "rm -f" command as likely unneeded.
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.

None yet

2 participants