 Relationships |
|
| Anonymous | Login | Signup for a new account | 2010-02-27 10:37 CET |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| 0000010 | [CapiSuite] scripts | feature | always | 2003-03-23 12:43 | 2003-03-23 12:44 | |||||||
| Reporter | gernot | View Status | public | |||||||||
| Assigned To | gernot | |||||||||||
| Priority | low | Resolution | open | |||||||||
| Status | assigned | Product Version | ||||||||||
| Summary | 0000010: add option for site-packages directory to configure | |||||||||||
| Description |
configure should allow to set directory for site-packages install explicitly. Achim Bohnet wrote: > Proper debian way would be: > > conf-make-install stuff to /usr/local/lib/pythonx/site-packages > private deb pkgs into /usr/lib/pythonx.x/site-packages [...] > Yes, work's here. It's Debian's policy is to not install anything in > /usr/local Nevertheless the packages are build (whenever possible) to also > search the corresponding /usr/local/x/y/z. Examples are PATH, > perl, python, emacs, ... |
|||||||||||
| Additional Information | ||||||||||||
| Attached Files | ||||||||||||
|
|
||||||||||||
|
Relationships |
|
| There are no notes attached to this issue. |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
