Date: Thu, 6 Aug 2009 18:12:44 -0400 From: "Jason J. Hellenthal" <jasonh@DataIX.net> To: Buganini <buganini@gmail.com> Cc: jasonh@dataix.net, freebsd-ports@freebsd.org Subject: Re: ports/*/jpeg "Thanks a lot guys" Message-ID: <20090806181244.f41bc316.jasonh@DataIX.net> In-Reply-To: <e5b1e8d40908052146p1fc07520l697f9262f21ed7d5@mail.gmail.com> References: <20090731121249.538ea7e7.jasonh@DataIX.net> <4A740679.1020608@infracaninophile.co.uk> <c/bsZ0e9iU@dmeyer.dinoex.sub.org> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
I believe unless I misunderstand what you are meaning, is the same thing that PORTREVISION is meant for doing. If the maintainer like what has just recently happened for jpeg bumps the PORTREVISION up one for every port that depends on jpeg then any upgrade utilities see that port as a new version and upgrade them happily.
PORTREVISION is the end of the package name as package-VERSION-{ , or _ }PORTREVISION.
Personally I feel that adding another NODE_VERSION as your saying could possibly be a benefit but at this time would cause a lot of maintainer overhead on which that they already have. I think more of a short written policy or checklist system for a maintainer might be a better route. Or possibly a ticket system built around a dependency checklist that should be fulfilled before a commit on a newer version would happen. Even with the previous statement that still causes overhead in workload but eventually speeds the process up due to lack of errors and re-corrections that have to be made ultimately resulting in a higher percent of satisfied hobbyists and customers alike thus bringing in more revenue.
If I could be of more assistance on this matter I have great experience satisfying time tested analytics that speed up processes in the form of Lean Manufacturing also plays a role in development.
Best regards.
On Thu, 6 Aug 2009 12:46:12 +0800
Buganini <buganini@gmail.com> wrote:
> Recently I'm think about how to make ports easier to upgraded:
> 1) Add a NODE_VERSION in each ports' Makefile, this variable would be stored
> in +CONTENTS.
> 2) Add a volatile-meaning flag in description of dependencies
>
> When a port, A, whose NODE_VERSION in Makefile > NODE_VERSION in +CONTENTS,
> ports that volatile'ly depends on A would be rebuilt.
>
> Any comment is welcome
>
> --Buganini
--
Jason J. Hellenthal
+1.616.403.8065
jasonh@DataIX.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090806181244.f41bc316.jasonh>