shadowfacts
/
Tusker
2
10
Fork 2
Code Issues 78 Pull Requests Releases Wiki Activity

xcconfigs? #308

New Issue
Closed
opened 2022-12-14 03:39:50 +00:00 by saagarjha · 3 comments
saagarjha commented 2022-12-14 03:39:50 +00:00
Copy Link

It seems like I'm going to have to deal with this conflict forever so I was wondering if you'd be open to migrating your build settings to xcconfigs, which would let me not have to deal with this anymore.
image

It seems like I'm going to have to deal with this conflict forever so I was wondering if you'd be open to migrating your build settings to xcconfigs, which would let me not have to deal with this anymore. ![image](/attachments/01bfc55d-4b97-432b-a0ef-e948e1a6859e)
image.png
208 KiB
shadowfacts commented 2022-12-14 04:44:10 +00:00
Owner
Copy Link

Yeah, definitely. The only reason I haven't done so already is that no one else has ever wanted to contribute.

Yeah, definitely. The only reason I haven't done so already is that no one else has ever wanted to contribute.
saagarjha commented 2022-12-15 12:42:52 +00:00
Author
Copy Link

Probably also worth changing these?

1f37a5e7eb/Tusker/Tusker.entitlements (L9)
1f37a5e7eb/Tusker/LocalData.swift (L34)

Probably also worth changing these? https://git.shadowfacts.net/shadowfacts/Tusker/src/commit/1f37a5e7ebd98d3391f2f7809263e10ab91b93a0/Tusker/Tusker.entitlements#L9 https://git.shadowfacts.net/shadowfacts/Tusker/src/commit/1f37a5e7ebd98d3391f2f7809263e10ab91b93a0/Tusker/LocalData.swift#L34
shadowfacts commented 2022-12-15 15:18:34 +00:00
Owner
Copy Link

I don't think there's a great way of dealing with this. The only option for modifying the entitlements seems to be completely replacing the file, which I'd rather not do because of the possibility of them getting out of sync.

I don't think there's a great way of dealing with this. The only option for modifying the entitlements seems to be completely replacing the file, which I'd rather not do because of the possibility of them getting out of sync.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
develop
compose-redesign
compose-rewrite
public-beta
release
calckey
async
simple-swift-promises
pixelfed
2024.4-136
2024.4-135
2024.4-134
2024.3-133
2024.3-132
2024.3-131
2024.3-130
2024.3-129
2024.3-128
2024.3-127
2024.3-126
2024.3-125
2024.2-124
2024.2-122
2024.2-121
2024.2-120
2024.1-119
2024.1-118
2024.1-117
2024.1-116
2024.1-115
2024.1-113
2024.1-112
2024.1-111
2023.8-110
2023.8-109
2023.8-107
2023.8-106
2023.8-105
2023.8-104
2023.7-103
2023.6-100
2023.5-98
2023.5-97
2023.5-96
2023.5-94
2023.5-91
2023.5-89
2023.5-84
2023.5-83
2023.5-81
2023.5-80
2023.5-77
2023.4-76
2023.4-75
2023.4-74
2023.4-73
2023.4-72
2023.4-71
2023.4-70
2023.3-69
2023.2-68
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
external

Issue depends on changes to external projects.

  
help wanted

Need some help

  
invalid

Something is wrong

  
investigate

An unconfirmed issue

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
duplicate
enhancement
external
help wanted
invalid
investigate
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: shadowfacts/Tusker#308
No description provided.
Delete Branch "%!s(<nil>)"

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?