Merge lp:~bac/lpsetup/xbit into lp:lpsetup
| Status: | Merged |
|---|---|
| Approved by: | Brad Crittenden on 2012-08-24 |
| Approved revision: | 78 |
| Merged at revision: | 78 |
| Proposed branch: | lp:~bac/lpsetup/xbit |
| Merge into: | lp:lpsetup |
| Diff against target: |
11 lines (+1/-1) 1 file modified
lpsetup/subcommands/init_target.py (+1/-1) |
| To merge this branch: | bzr merge lp:~bac/lpsetup/xbit |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Benji York (community) | code | 2012-08-24 | Approve on 2012-08-24 |
|
Review via email:
|
|||
Commit Message
Invoke launchpad-
Description of the Change
When lpsetup is installed, the script lpsetup/
It looks like there is a bug in the installer (acknowledged but not fixed). The easiest work-around is to just call it via invoking /bin/sh on the script instead.
| Brad Crittenden (bac) wrote : | # |
Good point Benji. Rather than do what you suggest long-term, I think it wiser to just figure out how to make setup.py not drop the execute bit. After discussion with you decided to land this branch with the risk you pointed out.

This is OK, I suppose. It does worry met that if the shebang ever
changes to another shell -- say /bin/bash -- and the script takes
advantage of non-sh features, then this could break in mysterious ways
(and the script when run stand-alone will still work, adding to the
mystery).
I wonder if it is worth reading the first line of the script (at
execution time) to assert that it really should be run with /bin/sh.