Customizing after PPA install

I fully expect this problem is due to my lack of Linux knowledge, so please bear with me...

I've been successfully building XBMC out of the SVN for several months now and am comfortable with that process. All of those results were in my user directory which I had full access to from the desktop to modify things as needed. Yesterday I used the PPA for the first time and that worked just fine. Until I tried to paste in an existing sources.xml file with all of my config details. The XBMC folder in usr/share/whatever is owned by root and the desktop wouldn't let me paste into it.

I assume that I can terminal/sudo in order to copy things into the PPA-created location. If that's the case, I can look up the commands and keep going. But is this what I should be doing here, or am I missing something obvious? I'm expecting to do this for both sources.xml and any non-SVN skins like Aeon.

Thanks -

Blake

The settings on the PPA is in your home folder.
So it should go in
$HOME/.xbmc/userdata/

Note that .xbmc is a hidden folder in linux (any file/folder begining with a "." is hidden in linux) so you'll need to show hidden files in nautilus (or xbmc if you use it to copy)

Thanks. I'll take another shot at it tonight.

I've got another question since using the PPA has been broached... I too am VERY comfortable with the SVN right now. I saw the PPA announcement and was honestly puzzled - what exactly does the PPA "do" for me? Should I be switching to that? I ASSume it doesn't update like SVN, yes? It appeared to allow others to develop things for it but honestly I'm ignorant enough about Linux I just wasn't sure what the advantage was. Can someone sort of spell it out in small words? I did look at some of the linked pages for it but didn't try to do anything with it. I currently have 7.x Ubuntu on my box and both the package version of XBMC and the SVN installed and running WELL.

Thanks!:o

It's easy is the main one. Noone needs to check the README for dependencies, it's automatic. It works with aptitude in ubuntu so you get the benifits with that..

Basicly svn will probably be updated more often, although the ustable here is set to be built once a day (if it's nothing wrong with that specific compile).

The hidden files comment made the difference - once the .xbmc folder appeared I was good to go. Thanks again.

Okay, makes some sense. Does this mean that the previous package system won't be used moving forward?

BLKMGK Wrote:Does this mean that the previous package system won't be used moving forward?

Which previous package system? PPA on Launchpad.net is the first and only pre-package system we got so far.

...if you are talking about SVN then understand that is not a package system, so it will contuinue on as always, no change there.

PPA is for user-friendliness and we will always know exacly what the end-user got when they use a specific PPA, PPA will also enable more people to try out XBMC in a simpler way. The SVN is really only for developement and debugging purposes (and for advanced/expert users who do not really need any suppport from anyone, people who are instead more likely to help others), so only if you like to say on the bleeding-edge and have the latest and greatest then the updated SVN revisions is what you will continue to use.

Okay, I had misunderstood the PPA announcement as something new having come out - I had previously setup the packaged version for testing and got the impression that PPA was somehow different. Relieved that it's the same because that means I don't have to do anything to "upgrade" on that version.

I do run the SVN and update pretty often, I also TRY to help others I'm comfortable with SVN but will try to have the packaged version running as for backup and to become familiar with it.

Appreciate the explanation!

Hopefully, all of us enthusiasts are trying out each new PPA version for a week or two for testing. That way we can move towards feature-completion and eventual beta and then release of 2.1 final.