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

docs: Fix LICENSE files for windows and linux #1431

Merged
merged 2 commits into from
Mar 13, 2023
Merged

Conversation

luanpotter
Copy link
Member

@luanpotter luanpotter commented Mar 13, 2023

Description

Flipping through pub I figured that unlike the AP-base package and all other AP packages, the Windows and Linux packages did not seem to have a LICENSE file associated.

image

Looking at GitHub, it was a simple mistake - the "symlink" was copied in a way that didn't propagate the correct file type when those packages were created.

They actually had physical files with the path of the symlink written on them. A fresh ln -s quickly amended the issue. The diff on GitHub web interface might look weird, but if you check git, what really changed was just the file type.

This should fix the pub issues with those two packages on the next release.

Before:
image

Now:
image

Checklist

  • The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs:, chore: etc).
  • I have read the Contributor Guide and followed the process outlined for submitting PRs.
  • I have updated/added tests for ALL new/updated/fixed functionality.
  • I have updated/added relevant documentation and added dartdoc comments with ///, where necessary.
  • I have updated/added relevant examples in example.

Breaking Change

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

Copy link
Collaborator

@Gustl22 Gustl22 left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -1 +0,0 @@
../../LICENSE
Copy link
Member

Choose a reason for hiding this comment

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

Symlinks don't play well with publishing packages, it's better to just have the license everywhere.

Copy link
Member Author

Choose a reason for hiding this comment

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

they do work! it was just these two weren't actually symlinks

Copy link
Member Author

Choose a reason for hiding this comment

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

other packages are good:
image

Copy link
Member

Choose a reason for hiding this comment

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

It's because I have a script that turns them from symlinks to real files every time I do a release 😂

Copy link
Member

Choose a reason for hiding this comment

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

And you ask me; "why didn't you just commit them as files instead of writing a script for that?"
image

Copy link
Member Author

Choose a reason for hiding this comment

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

well I will merge it so at least it is standard and shall work with your script
if you want to follow up and make them all copies, it's fine by me (as long as they are all consistent) :P
right now these two are files with symlink content so that definitely does not work at all

Copy link
Member

Choose a reason for hiding this comment

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

Makes sense: #1433

@luanpotter luanpotter merged commit 1f84e85 into main Mar 13, 2023
@luanpotter luanpotter deleted the luan.fix-licenses branch March 13, 2023 17:16
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.

3 participants