Comments on: Distributed distributions http://www.reactivated.net/weblog/archives/2007/06/distributed-distributions/ they got a skin and they put me in Thu, 08 Jan 2009 11:49:14 +0000 http://wordpress.org/?v=2.7 hourly 1 By: genstef http://www.reactivated.net/weblog/archives/2007/06/distributed-distributions/comment-page-1/#comment-14225 genstef Thu, 14 Jun 2007 10:57:18 +0000 http://www.reactivated.net/weblog/archives/2007/06/distributed-distributions/#comment-14225 For overlays.gentoo.org the usage you describe is already possible, see: http://www.kernel.org/pub/software/scm/git/docs/git-svn.html Unfortunately the official portage tree still uses cvs (and I see no real efforts of getting that fixed) :( For overlays.gentoo.org the usage you describe is already possible, see:

http://www.kernel.org/pub/software/scm/git/docs/git-svn.html

Unfortunately the official portage tree still uses cvs (and I see no real efforts of getting that fixed) :(

]]> By: Aldrik http://www.reactivated.net/weblog/archives/2007/06/distributed-distributions/comment-page-1/#comment-14221 Aldrik Thu, 14 Jun 2007 07:29:26 +0000 http://www.reactivated.net/weblog/archives/2007/06/distributed-distributions/#comment-14221 DSCM in general work on a workflow like : you clone locally you hack you make your local repository available or send the difference with main repository via mail DSCM in general work on a workflow like :
you clone locally
you hack
you make your local repository available or send the difference with main repository via mail

]]> By: Christian Faulhammer http://www.reactivated.net/weblog/archives/2007/06/distributed-distributions/comment-page-1/#comment-14220 Christian Faulhammer Thu, 14 Jun 2007 07:00:42 +0000 http://www.reactivated.net/weblog/archives/2007/06/distributed-distributions/#comment-14220 SourceMage uses Git. SourceMage uses Git.

]]> By: Donnie Berkholz http://www.reactivated.net/weblog/archives/2007/06/distributed-distributions/comment-page-1/#comment-14219 Donnie Berkholz Thu, 14 Jun 2007 04:37:09 +0000 http://www.reactivated.net/weblog/archives/2007/06/distributed-distributions/#comment-14219 Look into rPath. Their Conary system includes around the ability to branch and such. Look into rPath. Their Conary system includes around the ability to branch and such.

]]> By: Corey Burger http://www.reactivated.net/weblog/archives/2007/06/distributed-distributions/comment-page-1/#comment-14218 Corey Burger Thu, 14 Jun 2007 04:07:12 +0000 http://www.reactivated.net/weblog/archives/2007/06/distributed-distributions/#comment-14218 Debian and Ubuntu both maintain various packages in a decentralized way, both with git and bzr. For Ubuntu the kernel is in git and on kernel.org and the bzr maintained stuff can be found at https://wiki.ubuntu.com/BzrMaintainedPackages Debian and Ubuntu both maintain various packages in a decentralized way, both with git and bzr. For Ubuntu the kernel is in git and on kernel.org and the bzr maintained stuff can be found at https://wiki.ubuntu.com/BzrMaintainedPackages

]]> By: Jonathan Dehan http://www.reactivated.net/weblog/archives/2007/06/distributed-distributions/comment-page-1/#comment-14217 Jonathan Dehan Thu, 14 Jun 2007 03:08:05 +0000 http://www.reactivated.net/weblog/archives/2007/06/distributed-distributions/#comment-14217 I don't know any distros that do it, but how hard would it be for a decent scripter to hack together something that would set up the portage tree like this and give the correct permissions to the correct people? - Find out who is responsible for what ebuild, create the correct logins and random passwords, and see what happens? It would be real easy to add sync support in paludis ( check /usr/libexec/paludis/syncers/ for examples ). You could even make a hook on --sync to upload any individual's local overlay to the correct team responsible. I don't know how distributed scms work but maybe new ebuild could be skipped on a user's sync until they mark it official. This would keep the heirachy but also make it easy (and ecourage) people to maintain a few ebuilds and give back to the community/tree. If someone consistantly pumps out quality ebuilds, they can get permission to sync to the main tree... I don’t know any distros that do it, but how hard would it be for a decent scripter to hack together something that would set up the portage tree like this and give the correct permissions to the correct people? - Find out who is responsible for what ebuild, create the correct logins and random passwords, and see what happens? It would be real easy to add sync support in paludis ( check /usr/libexec/paludis/syncers/ for examples ). You could even make a hook on –sync to upload any individual’s local overlay to the correct team responsible. I don’t know how distributed scms work but maybe new ebuild could be skipped on a user’s sync until they mark it official. This would keep the heirachy but also make it easy (and ecourage) people to maintain a few ebuilds and give back to the community/tree. If someone consistantly pumps out quality ebuilds, they can get permission to sync to the main tree…

]]>