Re: 1.3.2 the grand finale?

On Aug 29, 2006, at 12:51 AM, Tabitha McNerney wrote:

> For the core maintainers of Darwin Ports, I am wondering if version 
> 1.3.2 is
> likely to be the grand finale before everything changes over to 
> "MacPorts"
> completely, with a subversion based repository?
>
> I would like to build a bunch of Darwin Ports from 1.3.2 on both PPC 
> and
> Intel Macs (each on HFSX disc volumes thank you Jordan Hubbard!) and am
> wondering if I should grab as many possible ports from 1.3.2 (even if I
> deactivate them) as possible since this might be the grand finale for 
> DP
> before the MP change?


	1.3.2 is certainly our last release before the macosforge switchover, 
which has already started on various aspects, the OpenDarwin cvs based 
repo --> macosforge svn based conversion happening this very afternoon, 
as James already explained on his message to this list.

	However, this is far from implying any kind of "cut off", "grand 
finale" or similar, our svn repo will look exactly the same as the 
current cvs one does, at least to begin with, and the sources (both the 
base darwinports tools and ports themselves) will remain the same until 
we put together a new release. So, in short, no need to rush building 
ports because of the switch. We do have some modifications on various 
fronts planned for the future, but rest assured that seamless migration 
paths will be provided where appropriate (most didn't noticed we 
switched from an rsync.opendarwin.org URL for sync/selfupdate to 
rsync.darwinports.org -- the same will likely happen again, this time 
to use rsycn.macports.org)

>
> Or, what would happen if I have a set of ports in the dependency chain 
> of
> ports based on 1.3.2 today and three months from now I want to tack on 
> a new
> port or an updated port. How difficult (if not impossible with MP) 
> will that
> be? Is there anyway to predict what might happen half a year from now 
> based
> on such a scenario in this very dynamic world we live, full of changes 
> and
> chaos at times?
>

	With respect to ports, they'll continue to evolve just as they do now 
once the svn repo goes live, nothing new here (so, again, no need to 
rush if you've been comfortable with our evolution so far). If you have 
a special need for any particular revision of a given Portfile, you'll 
be able to track down its history through our svn & trac portal that is 
yet to go live (we'll make the proper announcement in due time). The 
cvs history for each one of the files currently in our cvs repo will be 
imported into svn, so nothing will be lost.


> Best regards,
>
> T.
>

	In short, MacPorts will simply build on top of what DarwinPorts offers 
today, and nothing will change dramatically with respect to the 
management of installed ports (i.e. MacPorts will not deprecate them), 
at least not without proper planning and handling on our side ;-)

	Regards,...


-jmpp