[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Standardizing the layout of git packaging repositories

On 08/18/2014 07:47 AM, Henrique de Moraes Holschuh wrote:
> On Sun, 17 Aug 2014, Thomas Goirand wrote:
>> On 08/17/2014 03:52 AM, Raphael Hertzog wrote:
>>> On Fri, 15 Aug 2014, Henrique de Moraes Holschuh wrote:
>>>>> - the above layout is for the traditional case of non-native packages,
>>>>>   what would be the layout for native packages? how can be differentiate
>>>>>   between native/non-native layout?
>>>> Please don't.  It would be Really Troublesome should a package need to
>>>> switch from native to non-native, or the opposite.
>>> Why?
>>> Until we have defined what the layout is for a native package, you can't
>>> assume this. It's possibly a subset of the conventions for non-native
>>> packages + some common conventions in all software projects.
>>> Something like:
>>> - branches
>>>   - master: main development branch
>> Please don't use "master". It's meaningless. It just happens to be the
>> default in Git, but that's about it.
> It is not meaningless in the sense that it is a widely used convention in
> git repositories.

A widely used convention to express what? The fact that you didn't
bother changing the default name of the branch?


Reply to: