Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (3)
to General by Kalatti - 1 day, 17 hrs ago - more...
 |
|
2009-12-20
, 17:18
|
|
Posts: 1,070 |
Thanked: 1,604 times |
Joined on Sep 2008
@ Helsinki
|
#2
|
Originally Posted by lcuk
Better method:
is this plan doomed to failure, whats a better method?
Install everything into /opt/liqbase instead of the current path
Lazy method:
Add "maemo-optify" into debian/rules, immediately after dh_gencontrol.
More info about maemo-optify: http://maemo.gitorious.org/maemo-af/.../master/README
PS: This thread seems more suitable for the "developers" forum than this one.
| The Following User Says Thank You to VDVsx For This Useful Post: | ||
|
|
2009-12-20
, 17:23
|
|
Posts: 1,208 |
Thanked: 1,028 times |
Joined on Oct 2007
|
#3
|
Originally Posted by lcuk
Since there doesn't appear to be single package which owns /usr/share/liqbase directory, I would keep things simple&stupid and optify each package invidually. Nowadays it's as easy as saying "echo auto > debian/optify".
i would like to optify everything in one easy swoop and cure every single liqbase application with 1 symlink.
i just dont know how to do it
/usr/share/liqbase -----> /opt/liqbase
If you really want to something clever see how hard it is with python
 |
|
2009-12-20
, 17:25
|
|
Posts: 1,635 |
Thanked: 1,816 times |
Joined on Apr 2008
@ Manchester, England
|
#4
|
requires modification of all apps at once to work
and i mean a substantial run of changes around the system.
whilst the user aspects of liqbase are now flexible to change for users, lots of things still reference within /usr/share/liqbase... and frankly thats too big a change for now.
one shot deal to send 1 symlink is simpler
also, using the optify tool sounds like it would cause a bigger splash around the system and make it more prone to failure than the one single cure all inflection point I am considering.
and i mean a substantial run of changes around the system.
whilst the user aspects of liqbase are now flexible to change for users, lots of things still reference within /usr/share/liqbase... and frankly thats too big a change for now.
one shot deal to send 1 symlink is simpler
also, using the optify tool sounds like it would cause a bigger splash around the system and make it more prone to failure than the one single cure all inflection point I am considering.
__________________
liqbase sketching the future.
like what i say? hit the Thanks, thanks!
twitter.com/lcuk
liqbase sketching the future.
like what i say? hit the Thanks, thanks!
twitter.com/lcuk
|
|
2009-12-20
, 17:26
|
|
Posts: 1,208 |
Thanked: 1,028 times |
Joined on Oct 2007
|
#5
|
Originally Posted by VDVsx
I recommend the lazy method just because it's easier and often the result is better (in general case).
Lazy method:
Originally Posted by VDVsx
debian/optify is currently supported and much easier.
Add "maemo-optify" into debian/rules, immediately after dh_gencontrol.
|
|
2009-12-20
, 17:27
|
|
Posts: 1,635 |
Thanked: 1,816 times |
Joined on Apr 2008
@ Manchester, England
|
#6
|
mikkov
every single liqbase app requires the library to function
no liq* app can exist without first installing the library
hence the principle thing which creates anything there is the library itself
every single liqbase app requires the library to function
no liq* app can exist without first installing the library
hence the principle thing which creates anything there is the library itself
__________________
liqbase sketching the future.
like what i say? hit the Thanks, thanks!
twitter.com/lcuk
liqbase sketching the future.
like what i say? hit the Thanks, thanks!
twitter.com/lcuk
|
|
2009-12-20
, 17:29
|
|
Posts: 1,208 |
Thanked: 1,028 times |
Joined on Oct 2007
|
#7
|
Originally Posted by lcuk
modification is extremely simple. For "one shot" solution, which would probably be modifiation of libliqbase1 package, you would still have to modify all packages to make sure that updated libliqbase1 is installed.
requires modification of all apps at once to work
and i mean a substantial run of changes around the system.
whilst the user aspects of liqbase are now flexible to change for users, lots of things still reference within /usr/share/liqbase... and frankly thats too big a change for now.
one shot deal to send 1 symlink is simpler
also, using the optify tool sounds like it would cause a bigger splash around the system and make it more prone to failure than the one single cure all inflection point I am considering.
|
|
2009-12-20
, 17:30
|
|
Posts: 1,070 |
Thanked: 1,604 times |
Joined on Sep 2008
@ Helsinki
|
#8
|
Originally Posted by mikkov
Better than install directly into /opt ? Why ?
I recommend the lazy method just because it's easier and often the result is better (in general case).
|
|
2009-12-20
, 17:31
|
|
Posts: 1,208 |
Thanked: 1,028 times |
Joined on Oct 2007
|
#9
|
Originally Posted by lcuk
Sure, simple&stupid just tends keep away from unnecessary troubles.
mikkov
every single liqbase app requires the library to function
no liq* app can exist without first installing the library
hence the principle thing which creates anything there is the library itself
 |
|
2009-12-20
, 17:35
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#10
|
One uglier but also working option is let the preinst script create /usr/share/liqbase -> /opt/liqbase link, then let the packages unpack in /usr/share/liqbase as usual.
(which it isn't I don't know how to proceed barring knowing what I would like to do)
at the moment, the substantial media assets and everyday stuff for liqbase resides within
/usr/share/liqbase
ie:
/usr/share/liqbase/libliqbase
/usr/share/liqbase/liqbase-playground
/usr/share/liqbase/liqflow
/usr/share/liqbase/liqtorch
/usr/share/liqbase/liqcalendar
/usr/share/liqbase/liqacceltests
/usr/share/liqbase/liqtactoe
etc
i would like to optify everything in one easy swoop and cure every single liqbase application with 1 symlink.
i just dont know how to do it
/usr/share/liqbase -----> /opt/liqbase
since *everything* in liqbase requires this folder, and everything expects to use subdirs, changing that one inflection point should allow all standard liq* apps to work naturally without further tweaks.
i need to put something in the postinst/postrm of libliqbase to do this though.
any ideas about how/what/where/when???
is this plan doomed to failure, whats a better method?
liqbase sketching the future.
like what i say? hit the Thanks, thanks!
twitter.com/lcuk