BTW, 1.3.2 .dmg

[James Berry]

Hi Jyrki,

We "had" decided that we didn't need to create new dmg's for minor  
releases, as MacPorts will self update on install. This was in order  
to make the release process less cumbersome. But I agree that we  
haven't adequately documented this fact, and the world is confusing  
for somebody who just ends up in the downloads directory and doesn't  
understand why there is no dmg. Juan was going to better document  
this, but I'm not sure it happened.

I'll try to cut a new release (1.3.3) soon, with:

	- MacPorts name
	- A dmg

Secondarily, it turns out, we can't easily build a 1.3.2 dmg due to a  
bug in the 1.3.2 Makefile.

James

On Oct 17, 2006, at 5:30 AM, Jyrki Wahlstedt wrote:

> Hi,
> should someone package the current release as .dmg? Should the .dmg  
> (of the current, or next release) be named MacPorts?
>
> I saw that Ryan has mentioned this on Sep 11th, but with no answer  
> or action. Should a ticket be opened?
> !
> ! Jyrki Wahlstedt
> ! Kolmas linja 12 A 18            mob. +358-400-347 015  
> skype:jyrkiwahlstedt
> ! FI-00530 Helsinki               www.wahlstedt.fi
> !
> ! Our life is no dream; but it ought to become one and perhaps will.
> ! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0   
> A780 6366 EFD9 139C C386
>
>
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-dev/attachments/20061017/135eae81/attachment.html