Workflow for not blowing away state (was Re: [96136] trunk/base)

[Clemens Lang]

Hi,

On Wed, Sep 12, 2012 at 03:13:41PM -0700, Jeremy Huddleston Sequoia wrote:
> Is there an equivalently easy way to get base to think that the
> Portfile isn't newer?  What is everyone else's new workflow?

On Wed, Sep 12, 2012 at 06:19:09PM -0400, Jeremy Lavergne wrote:
> I usually edit the statefile (dot file inside work/).

I usually use -o, as Bradley already pointed out:

On Wed, Sep 12, 2012 at 03:36:12PM -0700, Bradley Giesbrecht wrote:
> Doen't "port -o" do what you want?
> 
> $ man port | col -b | grep -- " -o"
>      -o       honor state files even if the Portfile has been modified since
> 	      (called -o because it used to mean "older")

that still requires you to remember specifying -o, but I think that's
doable once you get used to it. If you want something different you
could write a small script that patches the statefile with the new
checksum:

for statefile in work/.macports.*.state; do
	sudo -u macports sed -i '' -E "s/^checksum: .*$/checksum: $(gsha256sum Portfile | cut -f 1 -d ' ')/g" $statefile
done

-- 
Clemens Lang