Author Archives: tabthorpe

The Ports Management Team 2013-03-06 17:25:04

The FreeBSD Ports Management Team wishes to remind users that February 28 was the end of support for the Ports Collection for both FreeBSD 7.4 RELEASE and the FreeBSD 7.x STABLE branch. Neither the infrastructure nor individual ports are guaranteed to work on these FreeBSD versions after that date. A tag has be created for users who cannot upgrade for some reason, at which time these users are advised to stop tracking the latest ports repository and use the RELEASE_7_EOL tag instead.

Read more at http://lists.freebsd.org/pipermail/freebsd-ports-announce/2013-March/000051.html

The Ports Management Team 2013-02-21 04:09:42

Mark Linimon, aka linimon@,  recently stepped down from his duties on the FreeBSD Ports Management Team.

Mark joined the team back in 2004, providing nine years of continuity to the Ports Infrastructure.  Among the many things Mark did, was maintaining and documenting the current portbuild system that the team uses for -exp runs and package building.  With his other bugbuster@ hat on, he played middle man contacting maintainers of BROKEN and DEPRECATED ports.

On behalf of the Ports Management team, we would like to thank Mark for his many years of service and dedication, his contributions will be greatly missed.

 

Thomas

on behalf of portmgr@

The Ports Management Team 2013-01-12 04:43:57

As announced in September the ports tree will no longer be exported to CVS after February 28th 2013. All users who still use CVS, CVSup or csup to update the ports tree are encouraged to switch to portsnap(8) or for users which need more control over their ports collection to use Subversion directly.

Read more at http://lists.freebsd.org/pipermail/freebsd-ports-announce/2013-January/000049.html

The Ports Management Team 2012-10-19 15:28:17

The FreeBSD Ports Management team is pleased to welcome Bernhard Froelich, aka decke@, to it’s ranks.

Bernhard was a long time ports contributor, and received his ports commit bit back in March 2010.

More recently, Bernhard was the one responsible for bringing us Redports.org shared tinderbox.

Please join me in welcoming decke@ to the team.

Thomas
on behalf of portmgr@

The Ports Management Team 2012-10-19 15:25:36

Pav Lucistnik, aka pav@, recently stepped down from his roll on the FreeBSD Ports Management team.

Pav started on portmgr back in November 2006, he was the one responsible for many of the -exp runs over the years. His most dubious claim to fame was talking over the responsibility of krismails. We all looked forwward to our pavmails, right?

On behalf of the Ports Management team, we want to thank Pav for his years of  service, he will be missed.
Thomas
on behalf of portmgr@

The Ports Management Team 2012-10-10 19:41:24

FreeBSD 9.1 RC2 has been pulicly announced, it is now time for the the Ports Feature Freeze.

Normal upgrade, new ports, and changes that do not affect other ports will be allowed without prior approval, but with the extra

Feature safe: yes

tag in the commit message. Any commit that is sweeping, that is, touches a large number of ports, infrastructural changes, commits to ports with unusually high number of dependencies, and any other commit that requires the rebuilding of many packages will not be allowed without prior explicit approval from portmgr@.

Check out http://www.freebsd.org/portmgr/implementation.html#sweeping_changes for what constiutes a sweeping change.
Thomas
on behalf of portmgr@

The Ports Management Team 2012-09-17 16:21:45

It was recently posted on, http://blogs.freebsdish.org/portmgr/2012/09/01/change-to-the-header-in-ports-makefiles/ that we would adopt a new header for the ports Makefiles. The initial discussion seemed to show enough support for the idea of completely stripping the header, leaving only the $FreeBSD$ tag. After the announcement was made, more people stated strong feelings that when and where possible attribution be maintained in the header.

A private discussion was held among ports committers, and while opinions were as varied as the individuals who shared them, it was decided to unify on a two line header.

# Created by: J.Q. Public <[email protected]>
# $FreeBSD$

The Whom line from the classic six line header becomes Created By.

Sometimes, as a result of a repocopy, or changed maintainership, the Created By and MAINTAINER is no longer in synchronisation. To avoid confusion, the first line can be removed, optionally leaving us with a one line header.

# $FreeBSD$

Removing the line of attribution is to be done only at the consent/request of the original contributor.

As before, we ask this header only be updated in conjunction with a regular update, as we do not want any unnecessary churn to the repo prior to the pending Ports Feature Freeze.

Thomas
on behalf of portmgr@

The Ports Management Team 2012-09-09 03:58:43

The development of FreeBSD ports is done in Subversion nowadays. For the sake of compatibility a Subversion to CVS exporter is in place which has some limitations. For CVSup mirroring cvsup based on Ezm3 is used which breaks regularly especially on amd64 and with Clang and becomes more and more unmaintainable.

Read more at http://lists.freebsd.org/pipermail/freebsd-ports/2012-September/078099.html

The Ports Management Team 2012-09-01 06:41:32

An idea has been floating around for some time, and it was brought up again on the ports@ mailing list recently, please remove the extraneous header information from the Makefile, leaving only the $FreeBSD$ id on the first line.

It is an idea that is long overdue, so from now on, the other fives lines shall be removed.

We do request that this be done sparingly in the short term, as we do not want to cause any additional churn on the repo as we approach our upcoming Ports Feature Freeze, still tentatively scheduled for September 7.

So please proceed only on existing updates. Please do not do any sweeping commits until we have the ports tree stablised post 9.1 tagging. Also bear in mind that Redports/QAT queues a job for every change done to a Makefile, we do not want to overburden the QAT at this time. It is important to allow this service to run at peek efficiency at this time to ensure it’s full potential as we approach the upcoming Feature Freeze.

The new look of the Makefile has been document in the Porter’s Handbook.

The next item on the todo list is to update devel/newfile for those that do a port create.

Thomas
on behalf of portmgr@

The Ports Management Team 2012-08-23 16:26:19

Florent Thoumie, aka flz@, recently stepped down from his roll on the FreeBSD Ports Management team.

Florent started on portmgr back in August 2008, being instrumental in maintaining the legacy pkg_* code plus other aspects of the ports infrastructure, including but not limited to the unifying of the code base for the ports build system.

On behalf of the Ports Management team, we want to thank Florent for his years of service, he will be missed.

Thomas
on behalf of portmgr@

The Ports Management Team 2012-08-02 06:18:53

After almost seven years, I figured it was about time for a new GPG key for the portmgr-secretary.

The key id is BBC4D7D5, the fingerprint is FB37 45C8 6F15 E8ED AC81 32FC D829 4EC3 BBC4 D7D5, and the public key is viewable at http://people.freebsd.org/~portmgr/portmgr-secretary.asc.

I have signed it with the old secretary key, as well as my own personal key.

Please update your keyring with the new info.

Thomas

FreeBSD 9.1 ports feature freeze

The FreeBSD 9.1 schedule has been published, http://www.freebsd.org/releases/9.1R/schedule.html. Historically we have done a Feature Freeze at RC1, we are going to try do it with RC2 this time, tentatively scheduled for August 3, subject to schedule slippage.

At the time the the Release Engineering team announces RC2 is ready, we will then enforce “Feature Safe” commits only. This means no sweeping changes will be allowed, see http://www.freebsd.org/portmgr/implementation.html#sweeping_changes

Once portmgr@ is satisfied that the requisite packages are built to ship with FreeBSD 9.1, the ports tree will be re-opened for business.

Thomas
on behalf of portmgr

Ports tree has been migrated to Subversion

The migration to Subversion is done and the SVN->CVS exporter is running.

Before committing please read the Ports Subversion Primer, http://wiki.freebsd.org/PortsSubversionPrimer. Please feel to add missing parts of fix it if something is wrong.

For those who like to mirror the repository, the svn mirror seed will be available in /pub/FreeBSD/development/subversion/ on a mirror near you. First places it will likely be are http://freebsd.isc.org/pub/FreeBSD/development/subversion/ and http://ftp.dk.freebsd.org/pub/FreeBSD/development/subversion/. Be aware that the uncompressed repository is about 14GB.

Many thanks to simon@ for all the work he did this weekend to make the switch happen!

Ports tree migration to Subversion

The FreeBSD ports tree will migrate from CVS to Subversion soon. The anticipated date for the migration is July 14th. This will have no impact for ports tree users as there will be a SVN to CVS exporter.

Please note that cvsup will still work after the migration. Nevertheless c(v)sup is pretty dated so you may want to see if portsnap(8) will fit your needs.

Beat and Thomas
on behalf of portmgr@

Please “Like” portmgr on Facebook

We recently migrated our Facebook profile so you can “Like” us, instead of “Join” us. Please make your way to http://www.facebook.com/portmgr and “Like” us.

The RSS feed from this blog should (hopefully) be setup to update our timeline on Facebook.

If you are completely into social media, you can also follow us on Twitter, http://www.twitter.com/freebsd_portmgr

Thomas
on behalf of portmgr@