Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 31 Jul 2011 19:18:00 +0000
From:      Baptiste Daroussin <bapt@FreeBSD.org>
To:        <freebsd-office@freebsd.org>
Subject:   Re: Developer Repository
Message-ID:  <b996b19424799c74634b9e15b285cdc9@etoilebsd.net>
In-Reply-To: <4E349AA8.4010201@FreeBSD.org>
References:  <4E349AA8.4010201@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 31 Jul 2011 01:58:32 +0200, Gabor PALI wrote:
> Hello there,
>
> If there is a team there should be a team repository as well :-)
> Currently we are working in Baptiste's github repository [1] but 
> perhaps
> we may have a common repository with all the ports that we want keep 
> in
> our focus.
>
> It would be beneficial for both users and developers:
>
> - "Early adopters" could access the work-in-progress ports easily and
> play with them.  Anybody could contribute to the project through the
> standard way of git/hg, i.e. clone/fork the repository, make her own
> modifications and then send us patches or pull requests.  Places that
> host such repositories also offer issue tracking and other fancy 
> stuff
> that may come useful in the long term.
>
> - There would be a common place where we could commit draft versions 
> of
> the ports for review/testing/etc.  Anybody without being a FreeBSD
> committer would be able to work in the repository.  These ports then 
> can
> be merged to the ports tree.  It is also a good way to share our
> "testing resources", i.e. anybody who has a spare box and time to 
> test
> the maintained ports can do test runs with them.
>
> As a bonus, there is a tool called portshaker(8) [2] that may be used
> for integrating the current state of our work with a snapshot of the
> Ports Collection.  This method also makes possible to store only the
> ports we want to develop.
>
> Thus I would suggest to place all our ports in such a repository and
> make it usable via portshaker(8).  A working example of this approach 
> is
> the FreeBSD Haskell repository at github [3] where I have been 
> working
> (with 200+ ports).  I have written a very simple script for
> "Perforce-like" integration [4] that helps to keep versions in the
> repository in synch with and the ports tree in a mergemaster(8)
> fashion.  In addition, I use the repository to periodically test all
> maintained ports together (and against) in a ports tinderbox.
>
> Opinions?
>
> Do you have any preferred servers/services?  In the first round, I 
> would
> suggest to use git and github, but feel free to recommend other :-)
>
>
> [1] https://github.com/bapt/libreoffice-ports/
> [2] http://www.freshports.org/ports-mgmt/portshaker/
> [3] https://github.com/freebsd-haskell/freebsd-haskell
> [4] http://people.freebsd.org/~pgj/haskell/merge-cvs-sdiff.sh
>
> _______________________________________________
> freebsd-office@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-office
> To unsubscribe, send any mail to 
> "freebsd-office-unsubscribe@freebsd.org"


I think it is a good idea, here is what can be done:

github with git
bitbucket with hg
google code with svn, git or hg
selfhosted with fossil.

What are your favorite choices ?

Bapt



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b996b19424799c74634b9e15b285cdc9>