Re-introduce build dir / dist dir option for isolated build environments. #933
No reviewers
Labels
No labels
accessibility
app-parity
area: creator
area: daemon
area: design
area: devops
area: discovery
area: docs
area: installer
area: internal
area: livestream
area: performance
area: proposal
area: reposts
area: rewards
area: search
area: security
area: subscriptions
area: sync
area: ux
area: viewer
area: wallet
BEAMER
channel
comments
community PR
consider soon
core team
css
dependencies
electron
Epic
feature request
first-timers-only
good first issue
hacktoberfest
help wanted
hub-dependent
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
merge when green
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
notifications
odysee
on hold
playlists
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
recsys
redesign
regression
resilience
sdk dependent
Tom's Wishlist
trending
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-desktop#933
Loading…
Reference in a new issue
No description provided.
Delete branch "readd-builddir"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR re-introduces the functionality for building lbry-app with a directory target. This is important for isolated build environments like solbuild (used for Solus), where build and install directories are different (and the contents of install dir are used in a final binary package) and thus necessitate being able to have unpackaged assets be placed in a directory relative to the build location, so instructions may be performed on those assets.
Note: This patch has already been tested with this commit to our package repo and validated locally.
@JoshStrobl Thanks for your contribution! Check out this for redeeming a reward.
@IGassmann it helps if you actually include the link 😛 https://lbry.io/faq/tips
But @JoshStrobl is a LBRY pro by now so I suspect he already knows he can get a reward for this. Thank you Josh!
Thanks for the quick review and merge @IGassmann. In terms of rewards, I'll pass (but it is appreciated). The patch was admittedly mostly self-serving, helps simplify the packaging process for the lbry-app on Solus and enables me to get it into the hands of users faster 😄