On 3/25/2013 5:50 AM, Jens Mueller wrote:
> how is Deimos supposed to address different versions of a library?
> In the case at hand, I have a Deimos repository for LLVM 3.1. Now I want
> to add support for version 3.2. Should I create a different branch or
> just a tag?


I think a branch for older versions would work best. "master" would be for the newest version.

On Monday, 25 March 2013 at 22:11:23 UTC, Walter Bright wrote:
> On 3/25/2013 5:50 AM, Jens Mueller wrote:
>> how is Deimos supposed to address different versions of a library?
>> In the case at hand, I have a Deimos repository for LLVM 3.1. Now I want
>> to add support for version 3.2. Should I create a different branch or
>> just a tag?
>
>
> I think a branch for older versions would work best. "master" would be for the newest version.

Or just not have a "master" branch at all. You can select the default branch in the GitHub repo admin settings.

David

On 3/25/2013 4:36 PM, David Nadlinger wrote:
> On Monday, 25 March 2013 at 22:11:23 UTC, Walter Bright wrote:
>> On 3/25/2013 5:50 AM, Jens Mueller wrote:
>>> how is Deimos supposed to address different versions of a library?
>>> In the case at hand, I have a Deimos repository for LLVM 3.1. Now I want
>>> to add support for version 3.2. Should I create a different branch or
>>> just a tag?
>>
>>
>> I think a branch for older versions would work best. "master" would be for the
>> newest version.
>
> Or just not have a "master" branch at all. You can select the default branch in
> the GitHub repo admin settings.

What's the point of that?

On Monday, 25 March 2013 at 23:49:22 UTC, Walter Bright wrote:
> On 3/25/2013 4:36 PM, David Nadlinger wrote:
>> On Monday, 25 March 2013 at 22:11:23 UTC, Walter Bright wrote:
>>> I think a branch for older versions would work best. "master" would be for the
>>> newest version.
>>
>> Or just not have a "master" branch at all. You can select the default branch in
>> the GitHub repo admin settings.
>
> What's the point of that?

Not having to worry about what the master branch should be. ;)

David

On Monday, March 25, 2013 16:49:22 Walter Bright wrote:
> On 3/25/2013 4:36 PM, David Nadlinger wrote:
> > On Monday, 25 March 2013 at 22:11:23 UTC, Walter Bright wrote:
> >> On 3/25/2013 5:50 AM, Jens Mueller wrote:
> >>> how is Deimos supposed to address different versions of a library?
> >>> In the case at hand, I have a Deimos repository for LLVM 3.1. Now I want
> >>> to add support for version 3.2. Should I create a different branch or
> >>> just a tag?
> >> 
> >> I think a branch for older versions would work best. "master" would be for the newest version.
> > 
> > Or just not have a "master" branch at all. You can select the default branch in the GitHub repo admin settings.
> 
> What's the point of that?

Well, since all the deimos stuff is is wrappers around released software, it would make sense that its version numbers always match the released software, in which case, master wouldn't really make sense unless it wrapped the currently developed version of the C library, which I wouldn't expect it to be doing in most cases.

- Jonathan M Davis

On Monday, 25 March 2013 at 12:50:49 UTC, Jens Mueller wrote:
> Hello,
>
> how is Deimos supposed to address different versions of a library?
> In the case at hand, I have a Deimos repository for LLVM 3.1. Now I want
> to add support for version 3.2. Should I create a different branch or
> just a tag?
>
> BTW I updated my documentation for creating Deimos repositories.
> http://jkm.github.com/d-programming-language.org/deimos.html
>
> Jens

We talked about that previously, but I'll say it here again for reference: You could use version identifiers and CTFE (the way I did with llvm-d). That way someone just has to download the deimos project and doesn't have to worry about getting the right branch every time he is on a different system. It also reduces the amount of redundant code as most of the code across different versions of the same library (for the C API anyway) will be the same and if you find a bug you don't have to look at all the other branches to see if it also needs to be fixed there.

Reading the rest of the posts here it doesn't seem like anyone favours it particularily, though, which is a pity.

Moritz

>
> We talked about that previously, but I'll say it here again for
> reference: You could use version identifiers and CTFE (the way I did
> with llvm-d). That way someone just has to download the deimos project
> and doesn't have to worry about getting the right branch every time he
> is on a different system. It also reduces the amount of redundant code
> as most of the code across different versions of the same library (for
> the C API anyway) will be the same and if you find a bug you don't have
> to look at all the other branches to see if it also needs to be fixed
> there.
>
> Reading the rest of the posts here it doesn't seem like anyone favours
> it particularly, though, which is a pity.
>
> Moritz

+1

Having used both, I favor it.