Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day, 16 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 1 day, 17 hrs ago -
Maemo repository (3)
to Community by torsen - 2 days, 9 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 3 days, 6 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 4 days, 13 hrs ago - more...
|
2010-02-09
, 14:50
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#92
|
Originally Posted by Bratag
The latest pianobar was done with the autobuilder instead of me doing it by hand. /usr/local is where pianobar installs itself normally if you were to build it from sources... it's all optified though... if you look in /usr/local you should just see links to pianobar into /opt/ somewhere.
Fatal latest pianobar version doubles up the app and has a bunch of stuff in /usr/local. Any chance we can get the old one back?
I had thought that when upgrading it would have removed the other one since it was tied to the old package.. I'll have to check it out. For the old one just use the one that is in testing instead of devel.
|
|
2010-02-09
, 14:52
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#93
|
Originally Posted by Bratag
I don't put a path into the code for pianobar I don't think.. so this would surprise me... if it's in both locations.. which I gathered from you saying it "doubled up"... then it should still work from either binary - one is just unnecessary. If it's only in the one place in /opt/usr/local then that's where it's supposed to be..?
The problem is related to the fact that pianobar in the new version changed location. So the front end tries to start it and its not where it should be.
Now I'm confused.
|
|
2010-02-09
, 15:04
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#94
|
Ok I just updated my scratchbox from the old version to the new and it *did* remove the link in /usr/bin/pianobar like it was supposed to and it's now in /usr/local/bin/pianobar which is where it normally *should* be.
It didn't clean up /etc/pianobar though which is a little annoying.. since the config location moved to /usr/local/etc/pianobar..
So if you've upgraded you can remove /etc/pianobar directory completely.
It still runs for me though.. after the upgrade:
So can someone run from the command line and see if it still works? Bratag - did you hard code /usr/bin/pianobar into qtPianobar? With python I was able to just "popen("pianobar")" and it pulled it out of the path instead of hard coding it.
ETA: Oh, because /etc/pianobar is a "config" file it won't remove it unless you "purge" pianobar first.. I see. I might have to put that into a postrm or something.
Last edited by fatalsaint; 2010-02-09 at 15:09.
It didn't clean up /etc/pianobar though which is a little annoying.. since the config location moved to /usr/local/etc/pianobar..
So if you've upgraded you can remove /etc/pianobar directory completely.
It still runs for me though.. after the upgrade:
Code:
[sbox-FREMANTLE_ARMEL: ~/pyPandora] > which pianobar /usr/local/bin/pianobar [sbox-FREMANTLE_ARMEL: ~/pyPandora] > pianobar Welcome to pianobar! [?] Username:
ETA: Oh, because /etc/pianobar is a "config" file it won't remove it unless you "purge" pianobar first.. I see. I might have to put that into a postrm or something.
__________________
If I've helped you or you use any of my packages feel free to help me out.
-----------------------------------------------------------------------------------
Maintaining:
pyRadio - Pandora Radio on your N900, N810 or N800!
If I've helped you or you use any of my packages feel free to help me out.
-----------------------------------------------------------------------------------
Maintaining:
pyRadio - Pandora Radio on your N900, N810 or N800!
Last edited by fatalsaint; 2010-02-09 at 15:09.
|
|
2010-02-09
, 15:12
|
|
Posts: 2,014 |
Thanked: 1,581 times |
Joined on Sep 2009
|
#95
|
Originally Posted by fatalsaint
I actually did hard code it, I was never sure if the path would include the location of the app. That being said I hate hard coding stuff.
Ok I just updated my scratchbox from the old version to the new and it *did* remove the link in /usr/bin/pianobar like it was supposed to and it's now in /usr/local/bin/pianobar which is where it normally *should* be.
It didn't clean up /etc/pianobar though which is a little annoying.. since the config location moved to /usr/local/etc/pianobar..
So if you've upgraded you can remove /etc/pianobar directory completely.
It still runs for me though.. after the upgrade:
So can someone run from the command line and see if it still works? Bratag - did you hard code /usr/bin/pianobar into qtPianobar? With python I was able to just "popen("pianobar")" and it pulled it out of the path instead of hard coding it.Code:[sbox-FREMANTLE_ARMEL: ~/pyPandora] > which pianobar /usr/local/bin/pianobar [sbox-FREMANTLE_ARMEL: ~/pyPandora] > pianobar Welcome to pianobar! [?] Username:
ETA: Oh, because /etc/pianobar is a "config" file it won't remove it unless you "purge" pianobar first.. I see. I might have to put that into a postrm or something.
__________________
Class .. : Power Poster, Potential Coder
Humor .. : [*********] Alignment: Chaotic Evil
Patience : [***-------] Weapon(s): +2 Logic Mace
Agro ... : |*****-----] Relic(s) : G1, N900
Class .. : Power Poster, Potential Coder
Humor .. : [*********] Alignment: Chaotic Evil
Patience : [***-------] Weapon(s): +2 Logic Mace
Agro ... : |*****-----] Relic(s) : G1, N900
|
|
2010-02-09
, 15:20
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#96
|
Originally Posted by Bratag
My fault.. it didn't occur to me it break the front-ends - I should have sent you a warning first when I realized the location was going to move having it auto-build instead of having me do it.
I actually did hard code it, I was never sure if the path would include the location of the app. That being said I hate hard coding stuff.
The only thing I don't like about the new one is the config location.. I would prefer it to stay in /etc/pianobar... I don't know of any app that uses /usr/local/etc for anything.. but pianobar doesn't come with an example config so I had to add it to the CMakeList files myself and evidently I am not fulling understanding the proper way to do it.
I'm not sure what to do at this point.. having auto-builder do it is the "proper" way to build the app.. do I leave it as is and you fix qtPianobar.. or do I find some way to pass an environment variable or something to auto-builder so that it builds in /usr/ instead of /usr/local ??
|
|
2010-02-09
, 15:24
|
|
Posts: 2,014 |
Thanked: 1,581 times |
Joined on Sep 2009
|
#97
|
Originally Posted by fatalsaint
Well ultimately I would like to see nothing in the /usr tree at all and certainly no configs in /etc. All apps should go into /opt as per optification rules to avoid using rootfs space. No configs should go into /etc that are not daemons or system level software. I much prefer the config in the user space.
My fault.. it didn't occur to me it break the front-ends - I should have sent you a warning first when I realized the location was going to move having it auto-build instead of having me do it.
The only thing I don't like about the new one is the config location.. I would prefer it to stay in /etc/pianobar... I don't know of any app that uses /usr/local/etc for anything.. but pianobar doesn't come with an example config so I had to add it to the CMakeList files myself and evidently I am not fulling understanding the proper way to do it.
I'm not sure what to do at this point.. having auto-builder do it is the "proper" way to build the app.. do I leave it as is and you fix qtPianobar.. or do I find some way to pass an environment variable or something to auto-builder so that it builds in /usr/ instead of /usr/local ??
__________________
Class .. : Power Poster, Potential Coder
Humor .. : [*********] Alignment: Chaotic Evil
Patience : [***-------] Weapon(s): +2 Logic Mace
Agro ... : |*****-----] Relic(s) : G1, N900
Class .. : Power Poster, Potential Coder
Humor .. : [*********] Alignment: Chaotic Evil
Patience : [***-------] Weapon(s): +2 Logic Mace
Agro ... : |*****-----] Relic(s) : G1, N900
|
|
2010-02-09
, 15:34
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#98
|
Originally Posted by Bratag
Well wait.. you and I are crossing here.
Well ultimately I would like to see nothing in the /usr tree at all and certainly no configs in /etc. All apps should go into /opt as per optification rules to avoid using rootfs space. No configs should go into /etc that are not daemons or system level software. I much prefer the config in the user space.
Pianobar is optified by maemo-optify. /opt is not a normal area and thus not usually added to $PATH because /opt can contain several different ideas:
/opt/package
/opt/maemo/package
/opt/maemo/bin
/opt/(insert random character that the developer decided he wanted here)
etc..
It's not consistent. So what you do is you create the directory tree.. just the directories (we're talking taking up a single inode here on the rootfs).. in the rootfs for like /usr/local/bin.
Then you link the application from the optified location, to the rootfs location.. so you get:
Code:
[sbox-FREMANTLE_ARMEL: ~/pyPandora] > which pianobar /usr/local/bin/pianobar [sbox-FREMANTLE_ARMEL: ~/pyPandora] > ls -al /usr/local/bin/pianobar lrwxrwxrwx 1 maemo maemo 33 Feb 9 08:07 /usr/local/bin/pianobar -> /opt/maemo/ usr/local/bin/pianobar
No real, noticeable, space is being taken on rootfs at all.
|
|
2010-02-09
, 15:44
|
|
Posts: 2,014 |
Thanked: 1,581 times |
Joined on Sep 2009
|
#99
|
Originally Posted by fatalsaint
Yeah thats perfect. Sorry think we had crossed wires there
Well wait.. you and I are crossing here.
Pianobar is optified by maemo-optify. /opt is not a normal area and thus not usually added to $PATH because /opt can contain several different ideas:
/opt/package
/opt/maemo/package
/opt/maemo/bin
/opt/(insert random character that the developer decided he wanted here)
etc..
It's not consistent. So what you do is you create the directory tree.. just the directories (we're talking taking up a single inode here on the rootfs).. in the rootfs for like /usr/local/bin.
Then you link the application from the optified location, to the rootfs location.. so you get:
So, the app itself is taking up space in /opt/maemo/usr/local/bin .. and something like 3 INODE's, and then a link to the other filesystem, is being taken up in Rootfs.Code:[sbox-FREMANTLE_ARMEL: ~/pyPandora] > which pianobar /usr/local/bin/pianobar [sbox-FREMANTLE_ARMEL: ~/pyPandora] > ls -al /usr/local/bin/pianobar lrwxrwxrwx 1 maemo maemo 33 Feb 9 08:07 /usr/local/bin/pianobar -> /opt/maemo/ usr/local/bin/pianobar
No real, noticeable, space is being taken on rootfs at all.
__________________
Class .. : Power Poster, Potential Coder
Humor .. : [*********] Alignment: Chaotic Evil
Patience : [***-------] Weapon(s): +2 Logic Mace
Agro ... : |*****-----] Relic(s) : G1, N900
Class .. : Power Poster, Potential Coder
Humor .. : [*********] Alignment: Chaotic Evil
Patience : [***-------] Weapon(s): +2 Logic Mace
Agro ... : |*****-----] Relic(s) : G1, N900
|
|
2010-02-09
, 15:49
|
|
Posts: 3,428 |
Thanked: 2,856 times |
Joined on Jul 2008
|
#100
|
Originally Posted by Bratag
Yeah.. the nice thing about maemo-optify in my rules file is it did all that for me. It however, did *not* appear to do it for my config file.. it's really in /usr/local/etc/pianobar/config.. that's not a link. Not a huge deal as the file itself is like 979 bytes or something.
Yeah thats perfect. Sorry think we had crossed wires there
So what I meant earlier was:
I'm not sure if we want to leave this as is, because this is way pianobar will be built from desktops down to little tablets... or if I should find a way to instead pass the make to /usr.
What this will do effectively, is put the app in /opt/maemo/usr/bin and link it to /usr/bin/ which is where the old version of pianobar I think was.
It'll also move the config file to /usr/etc/pianobar/.. at least unless I statically code the config to go somewhere..
Any suggestions welcome on where this package should reside.
Class .. : Power Poster, Potential Coder
Humor .. : [*********] Alignment: Chaotic Evil
Patience : [***-------] Weapon(s): +2 Logic Mace
Agro ... : |*****-----] Relic(s) : G1, N900