[HEADS UP] bsd-sharp-2.0 branched, PR sent

0 views
Skip to first unread message

Romain Tartière

unread,
Dec 21, 2008, 12:18:54 PM12/21/08
to bsd-...@googlegroups.com
Hi

Phillip did not write an announce so let's do a bit of communication
about BSD# status.


BIG NEWS! A problem report has been sent (ports/129724) [1] requesting
the update of the FreeBSD ports tree with the BSD#'s version of mono!

The commit will however not happen before FreeBSD 7.1 is out because
not sweeping changes are possible on ports until then [2,3].

For the moment, we only update existing ports. New ports will be
committed later, part of another problem report.

Anyway, the code lives in the BSD# repository for those who can't wait
;-).


Another important milestone: the source code has been branched. That
means that while we will continue to update the FreeBSD ports related to
Mono with mono-2.0 (the version that is about to reach the FreeBSD ports
tree), we are going to start playing with mono-2.2 preview releases.

We hope we will so be able to track mono release cycle and always
provide a recent Mono on FreeBSD.


Because of the branching, if you continue to track BSD#'s repository,
you now have to choose:
- you want to stay with a stable version of Mono (2.0) and track what
is going to be in the FreeBSD ports tree quite soon:

Track the ``bsd-sharp-2.0'' branch!

; or
- you want the bleeding-edge. The version of mono that is not going
to be in the FreeBSD ports tree soon (for the moment, mono-2.2),
bugs etc.
Track the ``trunk''!

Tracking the bsd-sharp-2.0 branch
=================================

Download and install portshaker>=0.0.7 (see bellow)

Edit /usr/local/etc/portshaker.conf, and as explained in comment,
replace ``bsd_sharp'' with ``bsd_sharp_releng_2_0'' at the end of the
line starting with ``main_merge_from''.


Tracking the trunk
==================

The default configuration provided in the example directory tracks the
trunk, so just install examples.

Installing portshaker
=====================

Download the tarball from Google-code [4] or checkout the code from the
code repository [5]. Installation is quite straightforward (just specify
DESTDIR):

$ tar zxf portshaker-0.0.7.tar.gz
$ cd portshaker-0.0.7
$ make DESTDIR="/usr/local"
$ sudo make DESTDIR="/usr/local" install

The tarball include a sample configuration for merging the BSD# ports
into the FreeBSD ports tree. To install it, just type-in:

$ cd examples
$ sudo make DESTDIR="/usr/local" install

Kind regards,
Romain


References:
1. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/129724
2. http://www.freebsd.org/releng/index.html#freeze
3. http://www.freebsd.org/portmgr/implementation.html#sweeping_changes
4. http://bsd-sharp.googlecode.com/files/portshaker-0.0.7.tar.gz
5. http://bsd-sharp.googlecode.com/svn/branches/portshaker/

--
Romain Tartière <rom...@blogreen.org> http://romain.blogreen.org/
pgp: 8DAB A124 0DA4 7024 F82A E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43)
(plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)

Phillip N.

unread,
Dec 22, 2008, 7:30:25 AM12/22/08
to bsd-...@googlegroups.com
El dom, 21-12-2008 a las 18:18 +0100, Romain Tartière escribió:
> Hi
>
> Phillip did not write an announce so let's do a bit of communication
> about BSD# status.
>

Thanks for all Romain!

Paul Hoffman

unread,
Jan 12, 2009, 2:11:16 PM1/12/09
to bsd-...@googlegroups.com
Soooo, what's the status of this? I just checked in everything, and /usr/ports/lang/mono, and there is no mono2 yet.

--Paul Hoffman

Paul Hoffman

unread,
Jan 12, 2009, 2:16:01 PM1/12/09
to bsd-...@googlegroups.com
[[ Resend, clearer. ]]

Soooo, what's the status of this? I just checked in everything, and /usr/ports/lang/mono is at 1.2, and there is no mono2 yet.

--Paul Hoffman

Phillip N.

unread,
Jan 13, 2009, 9:14:26 AM1/13/09
to bsd-...@googlegroups.com
El lun, 12-01-2009 a las 11:16 -0800, Paul Hoffman escribió:
> Soooo, what's the status of this? I just checked in everything,
> and /usr/ports/lang/mono is at 1.2, and there is no mono2 yet.
>
Yes, the PR has not been commited jet.
We will have to talk with wxs@ i guess.

PD: did you check my last mail about the eventually merge we could make
to solve the test that wasnot passing?

Thanks!

Reply all
Reply to author
Forward
0 new messages