Author vinay.sajip
Recipients alexis, eric.araujo, tarek, vinay.sajip
Date 2011-06-24.08:53:24
SpamBayes Score 6.0664e-07
Marked as misclassified No
Message-id <1308905605.65.0.75321405353.issue12393@psf.upfronthosting.co.za>
In-reply-to
Content
Some installation locations are platform-dependent and cannot be categorised into a small but fixed number of categories. This is particularly true for the Windows ecosystem - PowerShell, Office, SharePoint all have specific locations where files need to be installed for interoperability with them.

This can be catered for by a pre-hook for install_data, but some very small core changes are needed:

1. In the install_data constructor, initialise self.categories to an empty dictionary.
2. In install_data.expand_categories, add a  "local_vars.update(self.categories)" after the "local_vars = get_paths()" statement.

Just these small changes are sufficient to allow sufficient control over custom installation locations. For projects that need custom categories, they just need to do the necessary setup in an install_data pre-hook:

def pre_install_data(cmd):
    cmd.categories['customcategory'] = '/path/for/my/custom/category'

I have this working in the pythonv branch, and if the feature request is accepted I can work up a patch including changes to docs, tests etc.
History
Date User Action Args
2011-06-24 08:53:25vinay.sajipsetrecipients: + vinay.sajip, tarek, eric.araujo, alexis
2011-06-24 08:53:25vinay.sajipsetmessageid: <1308905605.65.0.75321405353.issue12393@psf.upfronthosting.co.za>
2011-06-24 08:53:24vinay.sajiplinkissue12393 messages
2011-06-24 08:53:24vinay.sajipcreate