Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 1 Jun 2008 21:15:20 -0400
From:      Matthew Donovan <kitche@kitchetech.com>
To:        "Aryeh M. Friedman" <aryeh.friedman@gmail.com>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: port maintaince procedural questions
Message-ID:  <20080602011520.GA38683@njord.Belkin>
In-Reply-To: <4843438B.2000807@gmail.com>
References:  <4843438B.2000807@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--fdj2RfSjLxBAspz7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Jun 01, 2008 at 08:49:15PM -0400, Aryeh M. Friedman wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> I have brought a older port maintained by ports@freebsd.org to the=20
> current version.... I have done all the work needed to make it=20
> committable.... I have several questions first:
>=20
> 1. How do I take maintainership of the port?
>=20
> 2. How do I submit the patch to bring it upto date? (I know for new=20
> ports I do PR with a special subject but in a case like this).
>=20
> Just so people know the port in question is devel/tailor I upgraded it=20
> from 0.9.32 to 0.9.34 because 34 has added 3 or so more back ends.
>=20
> As to the reason for asking for taking the maintainership is the ports=20
> 2.0 team needs it for internal development (we use aegis internally and=
=20
> need to translate to cvs).
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (FreeBSD)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>=20
> iEYEARECAAYFAkhDQ4sACgkQk8GFzCrQm4D7JACg2HYyxjzMrhOmCRKfjIYCTR4x
> C0YAn10z8fYSu7kjbADjNO6YvlXx2VMG
> =3Diz6w
> -----END PGP SIGNATURE-----
>=20
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
This is what I do anymore when I update a port I test it with porttools and=
 I copy the new port directory to something like <port>.new and leave the o=
ld port as is then I run port submit.=20

It will make the patch if it can find the older port and you fill out the P=
R and it will then ask to send it abort or nothing. it's the easiest way I =
have found.

--fdj2RfSjLxBAspz7
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkhDSagACgkQCyI5DJQdxQ/uMgCgiZ2lqVZcclHPlYNlX0WDOKBx
8y4AmgPkHHsxhlFNIXyKUIY5mkXjtSOX
=a8+m
-----END PGP SIGNATURE-----

--fdj2RfSjLxBAspz7--



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