Developer Repository
Baptiste Daroussin
bapt at FreeBSD.org
Sun Jul 31 20:10:52 UTC 2011
On Sun, 31 Jul 2011 20:54:54 +0100, Chris Rees wrote:
> On 31 Jul 2011 20:36, "Baptiste Daroussin" wrote:
> >
> > 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 Baptistes 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]
> >> [2] http://www.freshports.org/ports-mgmt/portshaker/ [3]
> >> [3] https://github.com/freebsd-haskell/freebsd-haskell [4]
> >> [4] http://people.freebsd.org/~pgj/haskell/merge-cvs-sdiff.sh [5]
> >>
> >> _______________________________________________
> >> freebsd-office at freebsd.org [6] mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-office [7]
> >> To unsubscribe, send any mail to
> "freebsd-office-unsubscribe at freebsd.org [8]"
> >
> >
> >
> > 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 ?
> >
>
> Are we anti-SF?
>
> Chris
>
> Links:
> ------
> [1] mailto:bapt at freebsd.org
> [2] https://github.com/bapt/libreoffice-ports/
> [3] http://www.freshports.org/ports-mgmt/portshaker/
> [4] https://github.com/freebsd-haskell/freebsd-haskell
> [5] http://people.freebsd.org/~pgj/haskell/merge-cvs-sdiff.sh
> [6] mailto:freebsd-office at freebsd.org
> [7] http://lists.freebsd.org/mailman/listinfo/freebsd-office
> [8] mailto:freebsd-office-unsubscribe at freebsd.org
No not at all except that I dislike the interface :)
btw you should be on honeymoon ? :)
Bapt
More information about the freebsd-office
mailing list