pombreda / pythonxy

Automatically exported from code.google.com/p/pythonxy
0 stars 1 forks source link

Installation Issues and Enhancement Requests #274

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Questions are answered below.  I also wrote document with screenshots.
See the Attached Document.

1. What version of Python(x,y) have you installed?
Version 2.6.6.2

2. Which components have you installed (Python(x,y) installer: 
I selected Recommended settings for All Users

3. Have you selected the option "Customize installation directories"?
No, I left it at default.   

4. If the answer to 3. is yes, what installation directories have you
chosen?
N/A

5. Where did you install Python(x,y) itself?
default path

6. Have you installed Python(x,y):
For "All users"

7. What is your operating system?
I tested the install with Windows XP and Windows 7 x64

8. When you installed Python(x,y), were you logged in as :
I was an administrator of the machine, I will be testing as least privledge
user at a later time.

9. If you are using Windows Vista, have you installed Python(x,y):
simply by double-clicking on the installer

10. Regarding installed softwares on your machine, how did you clean your
machine before installing Python(x,y) (multiple answers are possible):
I didn't do anything, I installed Python(x,y) directly on my
machine without precaution.  My machine was a clean machine already

Special notes and questions below:

Your documentation is unclear on your website. You state that there are silent 
install switches but you dont list what they are on your site.  I also notice
that you are installing redistributables, it would be helpful that those are
noted in the documentation.

My questions:
1. Are there alternate methods to installing Python x,y?
    such as: install Python.msi then install core plugins then install
    (x,y) core plugin...

2. Is there going to be an MSI version for Python (x,y)? 
    building an MSI would follow general best practices by using ICE and 
    ACE validation rules.

Please see the attached document for further notes.

Original issue reported on code.google.com by Rob.Las...@gmail.com on 29 Jul 2011 at 3:36

Attachments:

GoogleCodeExporter commented 9 years ago
Sorry,  I forgot to include my Enhancement requests.

Enhancement requests for adding commandline Switches.  As an admin we would 
deploy the software using our deployment tool which uses the System credentials.

1.  Have the ability to Log the installation.  Switch could be - /Log="Path"

2.  Have the ability to change the default "Install For" to "All Users".  
Switch could be - /Allusers=Yes or No  

3.  Plugins - Full or Recommended. switch could be - /Full

4.  Eclispse Workspace directory path. Switch could be - /Work="Path"

5.  Suppress or include Shortcuts.

Original comment by Rob.Las...@gmail.com on 29 Jul 2011 at 3:38

GoogleCodeExporter commented 9 years ago
This issue was closed by revision 2ebb136a1ea2.

Original comment by grizzly.nyo on 7 Aug 2011 at 9:29

GoogleCodeExporter commented 9 years ago
Wrong issue closed.

Original comment by grizzly.nyo on 8 Aug 2011 at 4:03

GoogleCodeExporter commented 9 years ago
I think #2 is already there in 2.6.6.2, or at least when you do a silent 
install it is.  "/S /ALLUSERS=1"

A lot of installers allow you to record an install and save the results of your 
configuration selections during that install to an answer file, which can then 
be called on the command line when doing a silent install.  This allows a lot 
more flexibility in deployment than just being able to select full or the 
default/recommended plugins and probably can fulfill all 5 enhancement requests 
if implemented completely.

Is this already possible with the installer, if not could it be added?  

Is python(x,y) using its own installer or is it using some other installer 
technology like installshield to build its setup file?

Original comment by tmfar...@gmail.com on 25 Aug 2011 at 4:11

GoogleCodeExporter commented 9 years ago
More information in regards to the installer.  Using a deployment tool such as 
Microsoft SCCM, Altiris or a LANDesk will cause broken shortcuts due to fact 
that they will use system accounts to install the software for Least Privilege 
accounts.  If this method is used and if you select Install for "Just me" 
during the component selection dialog.  The resulting installation will be 
successful however all the shortcuts will be broken or the file associations 
will be missing.  See the attached file.

Original comment by Rob.Las...@gmail.com on 27 Sep 2011 at 10:06

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by grizzly.nyo on 23 Feb 2012 at 8:13

GoogleCodeExporter commented 9 years ago
This issue was closed by revision 1026c8c7ac31.

Original comment by grizzly.nyo on 1 Mar 2012 at 1:29