![]() |
2009-12-30
, 20:23
|
|
Posts: 2,535 |
Thanked: 6,681 times |
Joined on Mar 2008
@ UK
|
#2
|
![]() |
2009-12-30
, 20:55
|
Posts: 402 |
Thanked: 229 times |
Joined on Nov 2009
@ Missouri, USA
|
#3
|
/usr/lib/python2.5/site-packages/aptly /usr/lib/python2.5/site-packages/aptly/aptly.py /usr/lib/python2.5/site-packages/aptly/COPYING /usr/lib/python2.5/site-packages/aptly/CHANGES /usr/bin/aptly
!#/bin/bash exec /usr/lib/python2.5/site-packages/aptly/aptly.py $@
![]() |
2009-12-30
, 21:18
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#4
|
The Following User Says Thank You to fatalsaint For This Useful Post: | ||
![]() |
2009-12-30
, 21:28
|
Posts: 486 |
Thanked: 251 times |
Joined on Oct 2009
|
#5
|
I don't know about the N900... but usually it's recommended in shell scripts to use #!/bin/sh ... for compatibility purposes with systems that either don't have bash, or have it in a different location.
At least.. that's what I've been told before..
(assuming you don't use bash-specific calls)
The Following User Says Thank You to j.s For This Useful Post: | ||
![]() |
2009-12-30
, 21:31
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#6
|
![]() |
2009-12-30
, 23:39
|
Posts: 402 |
Thanked: 229 times |
Joined on Nov 2009
@ Missouri, USA
|
#7
|
![]() |
2009-12-31
, 12:30
|
|
Posts: 2,535 |
Thanked: 6,681 times |
Joined on Mar 2008
@ UK
|
#8
|
/usr/bin/aptly contains the following:
Code:!#/bin/bash exec /usr/lib/python2.5/site-packages/aptly/aptly.py $@
#!/bin/sh exec /usr/lib/python2.5/site-packages/aptly/aptly.py "$@"
The Following 3 Users Say Thank You to Jaffa For This Useful Post: | ||
![]() |
2009-12-31
, 15:14
|
Posts: 402 |
Thanked: 229 times |
Joined on Nov 2009
@ Missouri, USA
|
#9
|
- To invoke the curses (or any GUI for that matter, should a) I place the appropriate script (for example aptly-curses.py) in /usr/bin as a python script or should I b) add that script to site-packages/aptly and write a script that calls it into /usr/bin?
- To call the command line variant, would I just make the /usr/bin/aptly script a bash script that calls the module passing it all arguments?
- Should the license and other documentation remain in /usr/share/doc/aptly, or should everything be moved (including aptly.py) to a directory named aptly under site-packagres instead?
Until I figure this out, I'm placing everything in site-packages except for aptly-cursesaspidites | blog | aspidites@inbox.com