DIP11
Steven Schveighoffer
schveiguy at yahoo.com
Thu Aug 11 05:52:47 PDT 2011
On Thu, 11 Aug 2011 03:49:56 -0400, Jacob Carlborg <doob at me.com> wrote:
> On 2011-08-11 09:41, Jonas Drewsen wrote:
>> On 11/08/11 09.07, Jacob Carlborg wrote:
>>> On 2011-08-10 21:55, jdrewsen wrote:
>>>> What is the status of DIP11
>>>>
>>>> http://www.wikiservice.at/d/wiki.cgi?LanguageDevel/DIPs/DIP11
>>>>
>>>> Has anyone started implementing it? Has it been rejected?
>>>>
>>>> /Jonas
>>>
>>> Not sure, personally I don't like it. Instead I'm working on a more
>>> traditional package manager called Orbit:
>>> https://github.com/jacob-carlborg/orbit/wiki/Orbit-Package-Manager-for-D
>>
>> Yes I've noticed that. Seems very promising.
>>
>> What I do like about DIP11 is how seamless it would work. You just have
>> to compile and stuff works.
>>
>> /Jonas
>
> I think that DIP11 is too limited, for example, it doesn't deal with
> versions. Orbit combined with a build tool will be seamless as well.
> RDMD is a great tool but as soon as you need to add compiler flags or
> compile a library you need either some kind of script or a build tool.
> And in that case you can just go with the built tool and have it work on
> all platforms.
Given that the implementation would be a compiler-used tool, and the tool
can implement any protocol it wants, I think it has very few limitations.
I envision the tool being able to handle any network protocol or packaging
system we want it to.
I think the benefit of this approach over a build tool which wraps the
compiler is, the compiler already has the information needed for
dependencies, etc. To a certain extent, the wrapping build tool has to
re-implement some of the compiler pieces.
-Steve
More information about the Digitalmars-d
mailing list