On Apr 17, 2017, at 8:26 PM, The Tick wrote:
>
> On 4/17/2017 9:11 PM, Ross Berteig wrote:
>> Try to avoid
>> preserving a version number as part of the folder names in the workspace
>> even if your upstream does that to you.
>
> So I've goofed up by putting freetype-2.7.1/
On 4/17/2017 7:26 PM, The Tick wrote:
.
So I've goofed up by putting freetype-2.7.1/ and others into the
repository?
"Goofed up" is too strong. "Picked a different way to do it" is more
accurate. There are tradeoffs and a lot of personal preference involved.
I guess I had assumed
Another option is to create a fossil for the 3rd party libraries, and then
open that fossil --nested in a directory inside your working directory.
Then nothing in that nested directory tree will be part of the main
fossil. You don't even need to commit to it if you don't want. Lastly,
when you
On 4/17/2017 9:11 PM, Ross Berteig wrote:
On 4/17/2017 6:50 PM, The Tick wrote:
I've put a project under fossil. Since it depends on a couple other
libraries, I've also put those into the repository so that I am not
dependent on being able to download those particular versions. Now,
when new
Hi Ross:
In message ,
Ross Berteig writes:
>On 4/17/2017 6:50 PM, The Tick wrote:
>> I've put a project under fossil. Since it depends on a couple other
>> libraries, I've also put those into the repository so that I am not
>> dependent on
On 4/17/2017 6:50 PM, The Tick wrote:
I've put a project under fossil. Since it depends on a couple other
libraries, I've also put those into the repository so that I am not
dependent on being able to download those particular versions. Now,
when new versions of those dependent libraries
I've put a project under fossil. Since it depends on a couple other
libraries, I've also put those into the repository so that I am not
dependent on being able to download those particular versions. Now, when
new versions of those dependent libraries become available, I want to
update my
7 matches
Mail list logo