[AG-DEV] Suggestion

[Tim Salmon]

Hi Jason and Andrew,
given the progress being made on the linux package side of things I think that is a sound suggestion.  I've not had time today but tomorrow I'll put some time into polishing things for windows environments.  the general solution (the guts of which is drawn from salim's work) will still achieve most things on most other platform but i definitely agree that this script should only be applied where upstream solutions are not available.

Individuals of course may adopt whatever we develop for particular circumstances: feedback always welcome.

Cheers,
Tim


-----Original Message-----
From: ag-dev-bounces at lists.mcs.anl.gov [mailto:ag-dev-bounces at lists.mcs.anl.gov] On Behalf Of Jason Bell
Sent: Thursday, 31 May 2012 4:24 PM
To: Andrew Danson; ag-dev at lists.mcs.anl.gov
Subject: Re: [AG-DEV] Suggestion

G'day All

If I can provide my 2 cents worth....

In regards to the Linux distro's - I wouldn't be that concerned with this operating system - as it is my understanding that Chris and Doug are looking to release new versions with appropriate changes applied (Not sure which distor's will be released - but I suspect some of the popular ones would be).  Therefore, the fix would simply to run the disto's equivalent of "package update".  Therefore, I'm not concerned too much with this.

What really concerns me is the Windows packages (focusing on Windows XP and Windows 7).  To build a new windows package will require a significant amount of work and I am not that confident that this will occur.  Therefore, I think the windows environment would benefit from the application of a "script" that fixes things.  Given that the location of the files is generally "fixed" on winxp or win7 environment, I would assume this shouldn't be that difficult.

In regards to Mac, given the audio side of things is still broken (rat), I am not sure how many people actually use the Mac client in a production environment, and I am sure a few information pages could be created to ensure mac users are catered for.

So - my opinion would be just to focus on configuring a script that "fixes" the windows clients!

Anyway, interested in what others think?

Regards,
Jason.


-----Original Message-----
From: ag-dev-bounces at lists.mcs.anl.gov [mailto:ag-dev-bounces at lists.mcs.anl.gov] On Behalf Of Andrew Danson
Sent: Thursday, 31 May 2012 09:22 AM
To: ag-dev at lists.mcs.anl.gov
Subject: [AG-DEV] Suggestion

Hi Salim and Tim,

May I make a suggestion with the script?

It seems from the feedback on the mail list that there is a lot of variation between the different operating systems and sometimes even between different versions ofthe same OS. Now rather than having to script every possible alternative, perhaps it would be best to make a sensible guess for each system as the default, and allow users of the script to specify the path either interactively (preferably) or on the command line when it fails.

Cheers
Andrew