Date: Fri, 7 Aug 2009 07:13:31 +0800 From: Buganini <buganini@gmail.com> To: "Jason J. Hellenthal" <jasonh@dataix.net> Cc: freebsd-ports@freebsd.org Subject: Re: ports/*/jpeg "Thanks a lot guys" Message-ID: <e5b1e8d40908061613y1151eb34h584983e4232adc92@mail.gmail.com> In-Reply-To: <20090806181244.f41bc316.jasonh@DataIX.net> References: <20090731121249.538ea7e7.jasonh@DataIX.net> <4A747C77.1040800@infracaninophile.co.uk> <20090801224323.GA65040@server.vk2pj.dyndns.org> <4A7552C8.7020508@infracaninophile.co.uk> <4A75A813.10307@infracaninophile.co.uk> <7d6fde3d0908030148h3b5a5934lb0ade13d8b095105@mail.gmail.com> <4A7724A7.6000500@FreeBSD.org> <7fX59uGuf0@dmeyer.dinoex.sub.org> <e5b1e8d40908052146p1fc07520l697f9262f21ed7d5@mail.gmail.com> <20090806181244.f41bc316.jasonh@DataIX.net>
next in thread | previous in thread | raw e-mail | index | archive | help
The meaning of NODE_VERSION and the flag is to describe dependencies more
detailed,
to make it possible to do automated upgrade, instead of bump PORTREVISION by
man.
An important thing, NODE_VERSION and the flag could be backward compatible,
for port/package don't have NODE_VERSION, it's just 0.
the flag could be just a '!' prefix, for example:
!fltk-threads>=1.1.9:${PORTSDIR}/x11-toolkits/fltk-threads
QT_COMPONENTS= gui imageformats_run moc_build !qmake_build !uic_build
without the flag, everything is just like how it is now.
this should be enough for cases like this jpeg case.
For more detail, if we only save NODE_VERSION of port itself in +CONTENTS
upgrade MUST be transactional, but for portupgrade and portmaster, exit in
half way is usual,
so I think to save NODE_VERSION of each dependencies is also necessary,
or even make it part of version string, but this may be confused for
somebody I think.
For the upgrade of perl, now we use port* -o to replace, then -r or -fr to
rebulid required-by
If we have
NODE_VERSION=5.8.0 in lang/perl5.8
NODE_VERSION=5.10.0 in lang/perl5.10
then when we port{upgrade,master} -o lang/perl5.10 perl5.8
we dont have to rebuild required-by manually anymore.
Furthermore, a unified target post-upgrade: is good, some ports has already
have this,
for example, upgrade-site-packages in lang/python
--Buganini
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e5b1e8d40908061613y1151eb34h584983e4232adc92>