pacman.conf NoExtract syntax for filelist over multiple lines

michis · 2016-01-14 23:35:13

Hi,

I couldn't figure out the corerct syntax for the NoExtract= option in pacman.conf
I want to do something like this

NoExtract = file1
            file2
            file3

writing all files in one line like this works

NoExtract = file1 file2 file3

but then it would be a really long line...

I tried it with a backslash at the line ends, but does not work.

NoExtract = file1 \
            file2 \
            file3

Do I have to write NoExtract= in every line like this?

NoExctract = file1
NoExctract = file2
NoExctract = file3

WorMzy · 2016-01-15 00:06:47

See https://wiki.archlinux.org/index.php/Pa … _to_system

Although I have a space-separated list of files:

NoExtract   = etc/fonts/conf.d/10-scale-bitmap-fonts.conf usr/share/xsessions/openbox-*

Which works just as well.

michis · 2016-01-15 00:26:16

ok, so if I understand the wiki right I have to put NoExtract= to the beginning of each line?
I thought there might be some syntax to avoid that...

Another thing:
I noticed the NoExtract option deletes files when the package is updated and a file is present in the filesystem.
E.g

Package A contains /usr/share/pixmaps/some-icon.png
I replaced this with another file and set
NoExtract = usr/share/pixmaps/some-icon.png

When package A is updated then pacman deletes /usr/share/pixmaps/some-icon.png
I thought the file will only not be installed.

Ok, then to prevent overwriting I have to use NoUpgrade=
That will create /usr/shre/pixmaps/some-icon.png.pacnew and keep my version of the file, that's what i want.
But in this case I don't want pacman to create a .pacnew file... and get the warnings every time the package is updated.

Is there an option to configure pacman to not create pacnew files for certain files in NoUpgrade= ?

Last edited by michis (2016-01-15 00:31:04)

x33a · 2016-01-15 05:41:28

michis wrote:

Another thing:
I noticed the NoExtract option deletes files when the package is updated and a file is present in the filesystem.
E.g
Package A contains /usr/share/pixmaps/some-icon.png
I replaced this with another file and set
NoExtract = usr/share/pixmaps/some-icon.png
When package A is updated then pacman deletes /usr/share/pixmaps/some-icon.png
I thought the file will only not be installed.

This sounds like a bug. Even if it is by design, you should open a report for the same on the bug tracker.

Ok, then to prevent overwriting I have to use NoUpgrade=
That will create /usr/shre/pixmaps/some-icon.png.pacnew and keep my version of the file, that's what i want.
But in this case I don't want pacman to create a .pacnew file... and get the warnings every time the package is updated.
Is there an option to configure pacman to not create pacnew files for certain files in NoUpgrade= ?

I am not aware of any such option. As for the warnings, it is to bring it to the user's attention, so that the user can merge the changes manually.

apg · 2016-01-15 06:05:38

michis wrote:

ok, so if I understand the wiki right I have to put NoExtract= to the beginning of each line?
I thought there might be some syntax to avoid that...
Another thing:
I noticed the NoExtract option deletes files when the package is updated and a file is present in the filesystem.
E.g
Package A contains /usr/share/pixmaps/some-icon.png
I replaced this with another file and set
NoExtract = usr/share/pixmaps/some-icon.png
When package A is updated then pacman deletes /usr/share/pixmaps/some-icon.png
I thought the file will only not be installed.
Ok, then to prevent overwriting I have to use NoUpgrade=
That will create /usr/shre/pixmaps/some-icon.png.pacnew and keep my version of the file, that's what i want.
But in this case I don't want pacman to create a .pacnew file... and get the warnings every time the package is updated.
Is there an option to configure pacman to not create pacnew files for certain files in NoUpgrade= ?

Add the file to both NoExtract and NoUpgrade.

x33a wrote:

This sounds like a bug. Even if it is by design, you should open a report for the same on the bug tracker.

This is the intended behavior. https://bugs.archlinux.org/task/39842

x33a · 2016-01-15 06:09:32

apg wrote:

x33a wrote:
This sounds like a bug. Even if it is by design, you should open a report for the same on the bug tracker.
This is the intended behavior. https://bugs.archlinux.org/task/39842

Thanks for the link. Maybe it should be better documented. But in my opinion, it shouldn't touch existing files at all.

michis · 2016-01-15 14:10:08

apg wrote:

michis wrote:
Is there an option to configure pacman to not create pacnew files for certain files in NoUpgrade= ?
Add the file to both NoExtract and NoUpgrade.

That's it, thanks.
Hm, maybe there should be an option IgnoreFile for such cases?

From the pacman.conf man page it was not clear to me that NoExtract beahves like if the file isn't in the package at all.

Last edited by michis (2016-01-15 14:10:22)

apg · 2016-01-15 15:29:08

michis wrote:

apg wrote:
michis wrote:
Is there an option to configure pacman to not create pacnew files for certain files in NoUpgrade= ?
Add the file to both NoExtract and NoUpgrade.
That's it, thanks.
Hm, maybe there should be an option IgnoreFile for such cases?

Why? Using NoExtract and NoUpgrade together already does what you want.

michis wrote:

From the pacman.conf man page it was not clear to me that NoExtract beahves like if the file isn't in the package at all.

Patches are of course welcome, but NoExtract does exactly what the documentation says: it prevents the extraction of the file during installation. It does absolutely nothing when the package is removed, which is the first step in upgrading the package.

michis · 2016-01-15 16:27:32

apg wrote:

michis wrote:
Hm, maybe there should be an option IgnoreFile for such cases?
Why? Using NoExtract and NoUpgrade together already does what you want.

Ok, it was just a quick idea that came into mind:

"Why use two options if it could be done with just one? If I want to put many files to NoUpgrade and NoExtract I have to write all the lines twice".

Humans are lazy...
But, yes the functionality is already there.
So never mind, as already mentioned it was just a not long thought about idea. "Hey would be nice if I could do this with just one option".

apg wrote:

It does absolutely nothing when the package is removed, which is the first step in upgrading the package.

"The package is removed first" , that's what I had not mind (removed completly first) but is necessary to understand why a file is deletetd if it's only in NoExtract.

Last edited by michis (2016-01-15 16:43:03)

x33a · 2016-01-16 10:31:29

Moving to "Pacman & Package Upgrade Issues".

Arch Linux

#1 2016-01-14 23:35:13

pacman.conf NoExtract syntax for filelist over multiple lines

#2 2016-01-15 00:06:47

Re: pacman.conf NoExtract syntax for filelist over multiple lines

#3 2016-01-15 00:26:16

Re: pacman.conf NoExtract syntax for filelist over multiple lines

#4 2016-01-15 05:41:28

Re: pacman.conf NoExtract syntax for filelist over multiple lines

#5 2016-01-15 06:05:38

Re: pacman.conf NoExtract syntax for filelist over multiple lines

#6 2016-01-15 06:09:32

Re: pacman.conf NoExtract syntax for filelist over multiple lines

#7 2016-01-15 14:10:08

Re: pacman.conf NoExtract syntax for filelist over multiple lines

#8 2016-01-15 15:29:08

Re: pacman.conf NoExtract syntax for filelist over multiple lines

#9 2016-01-15 16:27:32

Re: pacman.conf NoExtract syntax for filelist over multiple lines

#10 2016-01-16 10:31:29

Re: pacman.conf NoExtract syntax for filelist over multiple lines

Board footer