This repository has been archived by the owner on Mar 1, 2023. It is now read-only.
fixes #1: ensure unix line endings for script files in unix packages #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Going to test this... |
blaubaer
added a commit
that referenced
this pull request
Apr 11, 2013
fixes #1: ensure unix line endings for script files in unix packages
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed assembly configuration and pre-packaging script to ensure unix line endings for shell scripts that will end up in the unix packages.
Installing a locally built debian package worked fine (including autostart), but since I build on linux, this is not the ultimate test (which would be building on a windows machine).