Martin Costabel wrote: > Alexander Hansen wrote: >> Martin Costabel wrote: >>> Chupacerveza wrote: >>> >>>> I have a best practices question: if all I'm doing is updating the >>>> name of the maintainer and some usage notes, should I bump the >>>> revision number? >>>> thanks, >>>> >>> Yes. Anything that changes the contents of the *.deb file needs a new >>> rev. >>> >>> -- >>> Martin >>> >>> >> In practice, however, we often let that slide. > > Sure, I have often done this myself. But besides the change in *deb, > there is another point here: I think a change in the maintainer is such > an important event in the life of a package that it needs to be > identifiable by version-revision. Think of the web package database, for > example. To a lesser extent, this argument also holds for the usage > notes, if the updating is noticeable.
Well, for what it's worth, I just wanted to know whether packaging policy indicated that we should ask users to rebuild when there isn't a functional change to the package. I see that there are a couple of good reasons to do it and I also see that there may be times when that might be reconsidered. This package builds so quickly that it represents very little cost to do so, but I can imagine that there might be other packages or scenarios when it might be foregone. Thanks for the discussion! --Robert ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
