On Apr 25, 2011, at 10:36 AM, Ryan Schmidt wrote:

> 
> On Apr 6, 2011, at 05:36, [email protected] wrote:
> 
>> Revision: 77613
>>         http://trac.macports.org/changeset/77613
>> Author:   [email protected]
>> Date:     2011-04-06 03:36:53 -0700 (Wed, 06 Apr 2011)
>> Log Message:
>> -----------
>> doxygen: remove coreutils dependency, use BSD install instead. refs #28987
> 
> FYI, this probably didn't require a revision bump. All you've done is changed 
> *how* files are installed, but you haven't changed *what* files are 
> installed. The files a user will get by installing doxyegn @1.7.3_3 are 
> exactly the same as the ones they'll get by installing doxyegn @1.7.3_4. Keep 
> this in mind for future updates so you don't make people rebuild ports 
> unnecessarily.
> 

This is a dead-on observation and astute annalysis.

There is a far wider domain of application however, particularly
as MacPorts attempts binary packaging:

        Most "builds" don't change content at all but instead adjust metadata.

I see this everywhere with RPM as a "package manager" for years and the issue
of what a "build" is and does changes considerably as one develops "packaging" 
for
"content" distribution.

You might want to think through what "build" policy SHOULD apply
if/when you attempt binary packaging. There are many reasons for
rebuilding and version bumps and metadata dependency adjustments
involved with packaging.

73 de Jeff

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Reply via email to