Thanks Ryan, but even if I add the bin folder that the file external should
appear under to svn, I still can't bring the external file in - I get the
error that it failed. I've seen those release notes (which are echoed in the
latest book version) but the first paragraph about externals doesn't seem
clear to me at all about what is required.
Perhaps I'm thinking about this the wrong way. The benefit of bringing the
dll in directly to other people's projects is that they are restricted to a
particular release. The alternative is that they all check our 'team
library' out as a working copy alongside all their other wcs and add
references to it relatively but I just *know* at some point someone will
check in changes to that library wc inadvertently. As much as I want to
trust people not to screw up, I really could do with a way of *just* giving
them the binary tagged 'release' in their own svn projects.
2009/4/2 Ryan Schmidt <subversion-2009a_at_ryandesign.com>
> On Apr 1, 2009, at 12:09, Neil Trodden wrote:
>
>> The bin folder itself is not in source control but it's parent "Website"
>> is.
>>
>
> That's the problem. For file-based externals, the folder in which the
> external item appears must be versioned.
>
> If the book doesn't yet describe this, consult the release notes:
>
> http://subversion.tigris.org/svn_1.6_releasenotes.html#externals
>
>
--
Neil Trodden
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1516873
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-02 13:45:30 CEST