--
You received this message because you are subscribed to the Google Groups "docker-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to docker-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hi,as a gentoo user, i think i can volunteer. Its not easy to get an official ebuild into gentoo, though you can provide a build in an "overlay" Thats something similar to a PPA but source based.Its not my primary interest, but i think it should be done.
Current state in gentoo is:just do a make and it works
Thats one of the reasons i use gentoo. building form source just works.
So there is not so much special to do, beside depending on go.
PKG=github.com/kr/pty REV=27435c699; git clone http://$PKG $1/$PKG && (cd $1/$PKG && git checkout -f $REV)
PKG=github.com/gorilla/context/ REV=708054d61e5; git clone http://$PKG $1/$PKG && (cd $1/$PKG && git checkout -f $REV)
PKG=github.com/gorilla/mux/ REV=9b36453141c; git clone http://$PKG $1/$PKG && (cd $1/$PKG && git checkout -f $REV)
PKG=github.com/dotcloud/tar/ REV=d06045a6d9; git clone http://$PKG $1/$PKG && (cd $1/$PKG && git checkout -f $REV)
PKG=code.google.com/p/go.net/ REV=84a4013f96e0; hg clone http://$PKG $1/$PKG && (cd $1/$PKG && hg checkout $REV)
run cd /go/src/github.com/dotcloud/docker && hack/release/deps.sh /go/src
--
--
> Reasons for it i see are:
> - stability of earlier versions
> - simpler to make sure every build has the same result; less effort in
> maintaining
>
> Against it:
> - size
> - leaving choice to distros to use newer dependencies
There's something I find colossally absent from this list:
it's *semantically wrong* to put something like github.com/kr/pty in github.com/dotcloud/docker.
kr's pty library isn't in docker, and it's not written by dotcloud.
Here's a working example of how that hurts me, right now: I have a project that references the docker source, and also references the kr/pty source. Today, that project refers to both of them, and that works, and nothing's duplicated in my project, and it *makes sense semantically*. If the docker repo starts *also* including kr/pty as a giant cp'd blob with incoherent history, *my* project working tree now looks like absolutely incoherent slop.
Also, I'm in almost complete agreement with jpetazzo:
node_modules
into git for things you deploy, such as websites and apps.
--
You received this message because you are subscribed to the Google Groups "docker-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to docker-dev+...@googlegroups.com.
On Mon, Aug 26, 2013 at 10:05 PM, David Calavera <david.c...@gmail.com> wrote: