From a.janke at gmail.com  Sun Aug  6 16:58:42 2006
From: a.janke at gmail.com (Andrew Janke)
Date: Sun, 6 Aug 2006 16:58:42 -0400
Subject: [MINC-development] MINC 2.0 debian packages.
Message-ID: <d747ed50608061358g605a9db0k85329cb8568985aa@mail.gmail.com>

Hi all,

In a fit of productivity, I put together the vast majority of the MINC
packages compiled against MINC 2.0.11, they are here:

   http://packages.bic.mni.mcgill.ca/deb-minc2/

There is also the std Packages and Release file there so you should be
able to just modify your sources.list and get these ones.

A few things though that I am somewhat open to discussion about.

1. they install into /usr/local/bic -- This is for a number of reasons
but the most pertinent is that it will allow a clear differentiation
between minc 1.0 and 2.0 packages. ie: change your path and you are
minc2.0.

2. They use the same names as the old packages, this means that if you
install them they will upgrade your older minc 1.x versions and thus
remove them. You could always force them into apt and amke the old
ones stay there should you wish with a few -f's.  Reason?  I would be
loathe to start releasing all of these with a -minc2 prefix/suffix as
this is a broken approach to forward compatibility. besides we
advertise that things all backwards compatibile, so what is the
problem? :)

As always let me know if they work for you.  I would like to install
and test these at the BIC shortly (in parallel with what is already in
/usr/local/mni) The plan would be to freeze the install in
/usr/local/mni and work with /usr/local/bic until things "just work".


-- 
Andrew Janke   (a.janke at gmail.com || http://a.janke.googlepages.com/)
Canada->Montreal                                   Cell: +1 (514) 924 2012

From a.janke at gmail.com  Sun Aug  6 18:12:59 2006
From: a.janke at gmail.com (Andrew Janke)
Date: Sun, 6 Aug 2006 18:12:59 -0400
Subject: [MINC-development] [geeks] MINC 2.0 debian packages.
In-Reply-To: <eb9fb4b10608061421pb677572k862ba6e270b4e79@mail.gmail.com>
References: <d747ed50608061358g605a9db0k85329cb8568985aa@mail.gmail.com>
	<eb9fb4b10608061421pb677572k862ba6e270b4e79@mail.gmail.com>
Message-ID: <d747ed50608061512j74f07910h8362dfad853f409@mail.gmail.com>

On 8/6/06, Jonathan LAU <lau at bic.mni.mcgill.ca> wrote:
> The bic suffix is a bit confusing to me but I guess it's something we'll all
> have to just get used to.  Is there a reason for not using "minc2" itself as
> the suffix instead ( i.e. /usr/local/minc2/)?  That seems more
> self-explanatory to me.

Sounds like a grand plan, seems that we all missed the obvious.
(/usr/local/bic was Sylvains brainwave BTW).

I say we go even simpler and use /usr/local/minc, I will rebuild them
all using /usr/local/minc before public release.

I have an aversion to adding a "2" to the end of things when you
upgrade. I dislike this if only because then what do you do when you
release version 3?


a.

From jason at bic.mni.mcgill.ca  Sun Aug  6 18:49:00 2006
From: jason at bic.mni.mcgill.ca (Jason Lerch)
Date: Sun, 6 Aug 2006 18:49:00 -0400
Subject: [MINC-development] [geeks] MINC 2.0 debian packages.
In-Reply-To: <d747ed50608061512j74f07910h8362dfad853f409@mail.gmail.com>
References: <d747ed50608061358g605a9db0k85329cb8568985aa@mail.gmail.com>
	<eb9fb4b10608061421pb677572k862ba6e270b4e79@mail.gmail.com>
	<d747ed50608061512j74f07910h8362dfad853f409@mail.gmail.com>
Message-ID: <5B76ECFC-9567-444A-8EBC-610F5A72FA7B@bic.mni.mcgill.ca>


On 6-Aug-06, at 6:12 PM, Andrew Janke wrote:

> On 8/6/06, Jonathan LAU <lau at bic.mni.mcgill.ca> wrote:
>> The bic suffix is a bit confusing to me but I guess it's something  
>> we'll all
>> have to just get used to.  Is there a reason for not using "minc2"  
>> itself as
>> the suffix instead ( i.e. /usr/local/minc2/)?  That seems more
>> self-explanatory to me.

The intel-mac distro uses /usr/local/minc2 already, and I think  
keeping the 2 for the moment is great - at least for as long as  
people expect to be able to install both minc1 and 2 based software  
(I don't know why they would, but hey).

Jason

>
> Sounds like a grand plan, seems that we all missed the obvious.
> (/usr/local/bic was Sylvains brainwave BTW).
>
> I say we go even simpler and use /usr/local/minc, I will rebuild them
> all using /usr/local/minc before public release.
>
> I have an aversion to adding a "2" to the end of things when you
> upgrade. I dislike this if only because then what do you do when you
> release version 3?
>
>
> a.