Hi Derrick,
This use case can be solved using `pin --branch`.
If you really wanted to, you could also simply add B as a direct dependency of
P to specify a branch; there's no need to "nest" the dependency. If P really
does depend on B being on a branch, the manifest for P may be the right place
> On Jan 24, 2017, at 12:28 PM, Daniel Dunbar via swift-evolution
> wrote:
>
>
> https://github.com/apple/swift-evolution/blob/master/proposals/0149-package-manager-top-of-tree.md
I am in serious need of this feature for one of my projects, and the design
looks pretty good to me. +1.
--
B
Boris,
My Intent is to make it easier to develop dependency B. I may want to
develop on a feature branch for dependency B so I'd like to use PM to force
that to happen.
I don't want to have to cd into the A folder and then cd into B to make
that change. I want to control the whole thing from the
+1
This is an obvious (and much needed) enhancement!
While co-developing an application and a dependency package it’s annoying having
to create ‘dummy’ git tags to keep SPM happy.
-g.
___
swift-evolution mailing list
swift-evolution@swift.org
https://l
Hi Derrick,
I think you meant to send this as a reply to SE-0149 Package Manager Support
for branches, correct?
I’m not quite sure about the use case for your described behaviour, can you
elaborate a bit more why you would want to override a dependency of A from the
manifest of P?
If the goa
On 2017-01-24 20:28:30 +, Daniel Dunbar via swift-evolution said:
I am reposting this since the URLs were mangled in the original email.
Hello Swift community,
The review of SE-0149 “ Package Manager Support for Top of Tree
development" begins now and runs through January 31, 2017. The pr
> • What is your evaluation of the proposal?
It's a small improvement which will be very useful for a certain class of
people/projects. I see no downsides.
> • Is the problem being addressed significant enough to warrant a change
> to Swift?
Not significant for me, but quick enoug
>
>> On Jan 24, 2017, at 8:56 AM, Daniel Dunbar via swift-build-dev
>> mailto:swift-build-...@swift.org>> wrote:
>>
>> Hello Swift community,
>>
>> The review of SE-0149 “ Package Manager Support for Top of Tree development"
>> begins now and runs through January 31, 2017. The proposal is ava
It probably is a good idea.
Perhaps the changes can be done in the Package.swift file but allow nesting
of dependencies.
Suppose your dependency is like this where P is your current project
P --> A --> B
Normally P we would describe its dependency on A while B would be
abstracted away. In A, th
I am reposting this since the URLs were mangled in the original email.
Hello Swift community,
The review of SE-0149 “ Package Manager Support for Top of Tree development"
begins now and runs through January 31, 2017. The proposal is available here:
https://github.com/apple/swift-evolution/blo
10 matches
Mail list logo
