This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Stop a specific file from being overwritten when installing

Tags: None
(comma "," separated)
User avatar
Storm
Registered Member
Posts
77
Karma
0
OS
Hi!

I compile 2.9 from source on Linux. I want a specific file in the install folder (tags xml) to never be overwritten when installing, or, alternatively, automatically overwritten with my empty one after install.

How can I do this in a permanent and proper way? Can I make a patch to do this, or could maybe someone throw one together for me?

Note: I'm using the Animation/LOD branch but I think that shouldn't make a difference.


"Sic itur ad astra per aspera."
User avatar
halla
KDE Developer
Posts
5092
Karma
20
OS
Er, the tags.xml file isn't written to the installation directory, but to your user settings directory and is never overwritten when reinstalling a new version of Krita.
User avatar
Storm
Registered Member
Posts
77
Karma
0
OS
boudewijn wrote:Er, the tags.xml file isn't written to the installation directory, but to your user settings directory and is never overwritten when reinstalling a new version of Krita.

I'm talking about the default built in tags contained in:
INSTALL-DIR/share/apps/krita/tags/kis_paintoppresets_tags.xml

This file causes those annoying default tags to spam my tag list. Any default brush I did not blacklist yet will be put back under its default tag, and each tag will appear in the list, even if it is an empty tag (= I blacklisted all default brushes that belong to it). It will also automatically add the default tags with an empty "dummy" resource to my user tags file, so I have to prune them manually every time.

Since my workflow is based on my custom tags that, rather than categories, serve as specific toolkits for specific jobs so I can use them effectively as sets for the "favorites" ring , the default tags litter my UI.


"Sic itur ad astra per aspera."
User avatar
Storm
Registered Member
Posts
77
Karma
0
OS
bump


"Sic itur ad astra per aspera."
User avatar
halla
KDE Developer
Posts
5092
Karma
20
OS
Why the need to bump? If you've found the file, you can remove it after you do a make install. You shouldn't edit it, you should edit the local version in .kde -- but that's something that you probably could have figured out on your own.
User avatar
Storm
Registered Member
Posts
77
Karma
0
OS
I bumped because I didn't get an answer to my question. And I still didn't.

My question was how to automate this by, for example, patching some build files to exclude the installation of that file. Since I build fresh daily, it is really annoying having to go and manually delete it every single time. The whole point of my question was about how to avoid having to do it manually every time. I was editing it as an alternative of deleting because I wasn't sure if deleting causes error, so I just removed everything from in between <tags> and </tags>. I have my own tags in .kde... I just want to get rid of the default ones, and automatically.

I'm not an expert - I wouldn't asking if I was - but my understanding is that somewhere the install files tell the installer to install that specific file, and I thought maybe I could patch that out, but I have no idea how exactly it works, that's why I'm asking.


"Sic itur ad astra per aspera."
User avatar
halla
KDE Developer
Posts
5092
Karma
20
OS
You can patch calligra/krita/data/paintoppresets/CMakeLists.txt to not install the tag file.
User avatar
Storm
Registered Member
Posts
77
Karma
0
OS
boudewijn wrote:You can patch calligra/krita/data/paintoppresets/CMakeLists.txt to not install the tag file.

Thank you! That's exactly what I needed! :)


"Sic itur ad astra per aspera."


Bookmarks



Who is online

Registered users: Baidu [Spider], Bing [Bot], Google [Bot]