svn commit: r364287 - head/ports-mgmt/pkg-devel

[Tijl Coosemans]

On Mon, 11 Aug 2014 10:27:04 -0500 Bryan Drewery wrote:
> On 2014-08-11 04:21, Matthew Seaman wrote:
>> As I see it, if there's a change to any of the fields that go towards
>> creating the package digest, then we're requiring all the users to
>> update that package.  This should be avoided for trivial changes.
>> 
>> So, switching the question round: what fields in the manifest should
>> *not* imply reinstalling the package?
>> 
>>   - comment
>>   - description
>>   - categories  (these don't have much effect for binary packages)
>>   - www
>>   - maintainer  (hmmm... not sure.  We wouldn't want to have former
>>                  maintainers still being pestered about their old
>>                  ports.)
> 
> I would like to move all of this to a different mechanism. It is a lot 
> of BW overhead to download a new package only because a maintainer 
> changes, and then to also reinstall all files. I don't think we have 
> smart upgrades yet where only changed files are extracted (#735).
> 
> It also adds a lot of strain to the package building infrastructure to 
> be bumping revision for any of those fields. Yes it is the "proper" 
> thing, but it is not reasonable given all of the overhead. Generally 
> those things should be bunched up into other significant changes right 
> now.

Yes, ideally those 5 fields are updated by pkg in the local sqlite db
without fetching the entire package.