ports/graphics/netpbm out of date

Scot Hetzel swhetzel at gmail.com
Wed Mar 30 20:21:35 UTC 2011


On Wed, Mar 30, 2011 at 1:40 PM, Oliver Fromme <olli at lurza.secnetix.de> wrote:
> The current "stable" version is 10.47 (.27), and the current
> "advanced" version (this is not the development version!) is
> 10.53 (.05).
>
> I think that it makes sense to update the netpbm port to the
> "stable" version, and the netpbm-devel port to "advanced".
>
> However, the problem with that is that the netpbm folks don't
> provide tarballs anymore.  You have to check out the stuff
> from their SVN repository.  SourceForge provides a download
> URL that automatically packages the current source tree of a
> specified version (stable or advanced) and returns a .tar.gz
> file.  But of course you get a different .tar.gz file when a
> developer commits a patch, so this is not suitable as distfile
> for a FreeBSD port.  I'm not sure how to resolve that problem.
> Maybe upload a specific .tar.gz with a time stamp to a site
> that can be used as master site.
>
You can download a specific .tar.gz specific revision.

For stable branch 10.47.27:

http://netpbm.svn.sourceforge.net/viewvc/netpbm/stable.tar.gz?view=tar&pathrev=1443

For advanced branch 10.54.0:

http://netpbm.svn.sourceforge.net/viewvc/netpbm/advanced.tar.gz?view=tar&pathrev=1452

To get the revision for a specific version, look at the version.mk file,

http://netpbm.svn.sourceforge.net/viewvc/netpbm/advanced/

Then to get a consistant name for the tar file, the netpbm{,-devel},
port could add the following as a post-fetch target:

NETPBM_TRUNK=stable

.if defined(WITH_NETPBM_DEVEL)
:
NETPBM_TRUNK=advanced
NETPBM_REV=1452
:
.else
:
NETPBM_TRUNK=stable
NETPBM_REV=1443
:
.endif

post-fetch:
    if [ ! -f ${DISTDIR}/${PORTNAME}-${NETPBM_PORTVERSION}${EXTRACT_SUFX} ] ; \
      fetch -o ${DISTDIR}/${PORTNAME}-${NETPBM_PORTVERSION}${EXTRACT_SUFX}
http://netpbm.svn.sourceforge.net/viewvc/netpbm/${NETPBM_TRUNK}.tar.gz?view=tar&pathrev=${NETPBM_REV}
; \
    fi

I choose a post-fetch, so that we could define a MASTER_SITE to host
these tar files, and to allow the files to be fetched from FreeBSD
mirrors, that way we wouldn't cause a load on the SF site.

Scot


More information about the freebsd-ports mailing list