We've been experimenting with http://code.dlang.org for a while and things are going well. In particular Sönke has been very active about maintaining and improving it, which brings further confidence in the future of the project.

We're considering making dub the official package manager for D. What do you all think?


Andrei

On Tuesday, 10 September 2013 at 20:48:58 UTC, Andrei Alexandrescu wrote:
> We've been experimenting with http://code.dlang.org for a while and things are going well. In particular Sönke has been very active about maintaining and improving it, which brings further confidence in the future of the project.
>
> We're considering making dub the official package manager for D. What do you all think?
>
>
> Andrei

I vote yes but only if Sönke feels it is ready. I suspect he has a few things he'll probably want done before this happens (the potential switch from JSON to SDL comes to mind).

Am 10.09.2013 22:48, schrieb Andrei Alexandrescu:
> We've been experimenting with http://code.dlang.org for a while and
> things are going well. In particular Sönke has been very active about
> maintaining and improving it, which brings further confidence in the
> future of the project.
>
> We're considering making dub the official package manager for D. What do
> you all think?
>
>
> Andrei

I think it is a good idea.

Even if there are rough edges, it can be improved later on based on the community experience with it.

--
Paulo

On Tue, 10 Sep 2013 23:01:12 +0200
"Brad Anderson" <eco@gnuk.net> wrote:
> 
> I vote yes but only if Sönke feels it is ready. I suspect he has a few things he'll probably want done before this happens (the potential switch from JSON to SDL comes to mind).

I assume that would be a backwards-compatible change. Make SDL the preferred, but keep JSON in service.

How ready is it?

  1) bus factor.. what happens if Sonke disappears?
  2) backups?
  3) scaleability?
  etc?

On 9/10/13 1:48 PM, Andrei Alexandrescu wrote:
> We've been experimenting with http://code.dlang.org for a while and things are going well. In
> particular Sönke has been very active about maintaining and improving it, which brings further
> confidence in the future of the project.
>
> We're considering making dub the official package manager for D. What do you all think?
>
>
> Andrei

On 09/10/2013 04:48 PM, Andrei Alexandrescu wrote:
> We've been experimenting with http://code.dlang.org for a while and things are going well. In particular Sönke has been very active about maintaining and improving it, which brings further confidence in the future of the project.
> 
> We're considering making dub the official package manager for D. What do you all think?
> 
> 
> Andrei

votes++ over here
From my usage of it, it still has a couple of things that are in
development (a bit more of a user manual would be nice but I can attempt
to make one in my "free time"), but it's in a state now where it's
definitely usable for projects.
A friend and I are planning on making a little project for a game jam
this weekend, we'll try using dub and see what happens, but so far I'd
definitely say "yes"

-Matt Soucy

On Tuesday, 10 September 2013 at 20:48:58 UTC, Andrei Alexandrescu wrote:
> We've been experimenting with http://code.dlang.org for a while and things are going well. In particular Sönke has been very active about maintaining and improving it, which brings further confidence in the future of the project.
>
> We're considering making dub the official package manager for D. What do you all think?
>
>
> Andrei

Not big on package repository systems for languages, The amount
of crap that eventually accumulates from abandoned projects wears
down on its usefulness.

Examples being php-pear, php-pecl, python pypi, etc I am sure
their are more examples.

Mostly however it comes down to strong policy about what stays in
the main package management system.

Projects that haven't had an update for an excessive amount of
time should likely be hidden but still available except in cases
where it is known to be unchanged without need for updates(such
as most wrappers).

And license acknowledgement, this is much more important with
source libraries then it is with say apt on Ubuntu.  Accidentally
polluting a bsd project or a closed source project with LGPL/GPL
code would be very bad, And often these package management
systems obscure what the sources license actually is by simply
not showing it or informing the user.

Basically I suggest that after one year without an update a
package gets moved into a old packages list, or flagged as
hidden, Except where the author sets a flag that says the package
is a wrapper.

And when packages are fetched give a summary of the licenses
used, the license name should be enough, google can fill in the
rest if need be.

On 9/10/13 2:16 PM, Brad Roberts wrote:
> How ready is it?
>
>    1) bus factor.. what happens if Sonke disappears?
>    2) backups?
>    3) scaleability?
>    etc?

The whole point of making this a community project is to improve on all of the above. The way I see it the project should be a solid basis for further community development.

Andrei

On Tuesday, 10 September 2013 at 22:06:28 UTC, luminousone wrote:
> And license acknowledgement, this is much more important with
> source libraries then it is with say apt on Ubuntu.  Accidentally
> polluting a bsd project or a closed source project with LGPL/GPL
> code would be very bad, And often these package management
> systems obscure what the sources license actually is by simply
> not showing it or informing the user.
>

There is a license field in the dub package file.  It would be neat if dub could warn you if it found incompatible license in your dependencies though.

On Tuesday, 10 September 2013 at 20:48:58 UTC, Andrei Alexandrescu wrote:
> We're considering making dub the official package manager for D. What do you all think?

This would be awesome.
+1