[arch-general] pacman.conf: can I use wildcards?
I could not find any decisive answer in either the man page or on the web. Here's my question: in etc/pacman.conf, can I use entries such as: NoExtract = usr/share/man/man1/mkisofs* NoExtract = etc/logrotate.d/* or: NoUpgrade = etc/cron.daily/logrotate etc/logrotate.* clemens
On Wed, Feb 17, 2010 at 3:51 PM, clemens fischer <ino-news@spotteswoode.dnsalias.org> wrote:
I could not find any decisive answer in either the man page or on the web. Here's my question: in etc/pacman.conf, can I use entries such as:
NoExtract = usr/share/man/man1/mkisofs* NoExtract = etc/logrotate.d/*
or:
NoUpgrade = etc/cron.daily/logrotate etc/logrotate.*
No, we don't support globbing in these options. Question to the list- does it make sense to do so? -Dan
On Wed, Feb 17, 2010 at 8:13 PM, Dan McGee <dpmcgee@gmail.com> wrote:
On Wed, Feb 17, 2010 at 3:51 PM, clemens fischer <ino-news@spotteswoode.dnsalias.org> wrote:
I could not find any decisive answer in either the man page or on the web. Here's my question: in etc/pacman.conf, can I use entries such as:
NoExtract = usr/share/man/man1/mkisofs* NoExtract = etc/logrotate.d/*
or:
NoUpgrade = etc/cron.daily/logrotate etc/logrotate.*
No, we don't support globbing in these options. Question to the list- does it make sense to do so?
I think so. There could be enough files that listing them would be tedious, or it could be that one wants to exclude any future files of a given pattern, even though one doesn't know what they might be called.
On 18 February 2010 09:13, Dan McGee <dpmcgee@gmail.com> wrote:
On Wed, Feb 17, 2010 at 3:51 PM, clemens fischer <ino-news@spotteswoode.dnsalias.org> wrote:
I could not find any decisive answer in either the man page or on the web. Here's my question: in etc/pacman.conf, can I use entries such as:
NoExtract = usr/share/man/man1/mkisofs* NoExtract = etc/logrotate.d/*
or:
NoUpgrade = etc/cron.daily/logrotate etc/logrotate.*
No, we don't support globbing in these options. Question to the list- does it make sense to do so?
For those two, yes; we assume more users are likely to have a number of files there. -- GPG/PGP ID: B42DDCAD
Am Wed, 17 Feb 2010 19:13:26 -0600 schrieb Dan McGee <dpmcgee@gmail.com>:
No, we don't support globbing in these options. Question to the list- does it make sense to do so?
Yes, because I usually edit many of the .desktop files in /usr/share/applications due to a missing menu editor in Xfce and a terrible menu editor in KDE (bloated XML file and just marking entries as deleted instead of deleting them). And adding every single .desktop file to /etc/pacman.conf makes this file pretty long and complex. So it was nice, if one could either add a complete directory (e.g. usr/share/applications) or such a path with a wildcard for the files (e.g. usr/share/applications/*) to NoUpgrade. Greetings, Heiko
On 02/17/2010 10:13 PM, Dan McGee wrote:
On Wed, Feb 17, 2010 at 3:51 PM, clemens fischer <ino-news@spotteswoode.dnsalias.org> wrote:
I could not find any decisive answer in either the man page or on the web. Here's my question: in etc/pacman.conf, can I use entries such as:
NoExtract = usr/share/man/man1/mkisofs* NoExtract = etc/logrotate.d/*
or:
NoUpgrade = etc/cron.daily/logrotate etc/logrotate.*
No, we don't support globbing in these options. Question to the list- does it make sense to do so?
-Dan
Yes, sure! In many times, this will be really usefull. -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D
On Wed, Feb 17, 2010 at 7:13 PM, Dan McGee <dpmcgee@gmail.com> wrote:
On Wed, Feb 17, 2010 at 3:51 PM, clemens fischer <ino-news@spotteswoode.dnsalias.org> wrote:
I could not find any decisive answer in either the man page or on the web. Here's my question: in etc/pacman.conf, can I use entries such as:
NoExtract = usr/share/man/man1/mkisofs* NoExtract = etc/logrotate.d/*
or:
NoUpgrade = etc/cron.daily/logrotate etc/logrotate.*
No, we don't support globbing in these options. Question to the list- does it make sense to do so?
Yes, but it would also be nice to support recursion here as well. For instance: NoExtract = /usr/share/doc/* should disable ALL doc extraction, no matter how deep it's nested
On Wed, 17 Feb 2010 20:34:09 -0600, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
No, we don't support globbing in these options. Question to the list- does it make sense to do so?
Yes, but it would also be nice to support recursion here as well. For instance:
NoExtract = /usr/share/doc/*
should disable ALL doc extraction, no matter how deep it's nested
Recursion is a good idea but that's not what is usually expected from *. I would suggest to use ** like in ZSH if it is implemented. Real regular expressions support would solve all those problems but that's probably overkill.
On Thu, Feb 18, 2010 at 4:20 AM, Pierre Chapuis <catwell@archlinux.us> wrote:
On Wed, 17 Feb 2010 20:34:09 -0600, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
No, we don't support globbing in these options. Question to the list- does it make sense to do so?
Yes, but it would also be nice to support recursion here as well. For instance:
NoExtract = /usr/share/doc/*
should disable ALL doc extraction, no matter how deep it's nested
Recursion is a good idea but that's not what is usually expected from *. I would suggest to use ** like in ZSH if it is implemented. Real regular expressions support would solve all those problems but that's probably overkill.
Well, ** isn't valid in standard POSIX globbing and require additional coding to make it happen
Am Thu, 18 Feb 2010 11:20:11 +0100 schrieb Pierre Chapuis <catwell@archlinux.us>:
Recursion is a good idea but that's not what is usually expected from *. I would suggest to use ** like in ZSH if it is implemented. Real regular expressions support would solve all those problems but that's probably overkill.
It's just struck me that real regular expressions are no good idea for NoUpgrade, not only because that would be overkill but also because of the different meaning of the ".". In regexp it means a wildcard for one character, in the shell and file systems it's occasionally used in file names. Greetings, Heiko
At Donnerstag, 18. Februar 2010 02:13 Dan McGee wrote:
No, we don't support globbing in these options. Question to the list- does it make sense to do so?
Instead this makes something easier i must say that this could be dangerous too because it could end in some strange questions in the support area. Perhaps it could helps if you makes it possible to use a include file for this because than appending a file in this file is easier as to edit pacman.conf. This "harder way" for NoUpgrade has the advantage that you even know which file is the reason why you edit it because sometimes i don't know weeks or months later what i have done ... but this be more my self-critical 2c.-) See you, Attila
Attila wrote:
At Donnerstag, 18. Februar 2010 02:13 Dan McGee wrote:
No, we don't support globbing in these options. Question to the list- does it make sense to do so?
Instead this makes something easier i must say that this could be dangerous too because it could end in some strange questions in the support area.
Not likely. Files named like something/other*, with the star being a literal instead of a glob are very, very rare. On the contrary, people have provided good examples where wildcards are useful.
Perhaps it could helps if you makes it possible to use a include file for this because than appending a file in this file is easier as to edit pacman.conf. This "harder way" for NoUpgrade has the advantage that you even know which file is the reason why you edit it because sometimes i don't know weeks or months later what i have done ... but this be more my self-critical 2c.-)
That's what comments are for. Remember the '#' hash mark? clemens
At Donnerstag, 18. Februar 2010 19:30 clemens fischer wrote:
Not likely. Files named like something/other*, with the star being a literal instead of a glob are very, very rare.
There is no guarantee that this will be used in this way.-)
On the contrary, people have provided good examples where wildcards are useful.
That is true and every example was a good example. But there is a little risk that you got lazy if you don't document what you have done and than including a complete directory with a lot of files could end in a bugreport where people search a longer time because no one is thinking that it was "simple mistake". That is all what i want to say and myself wouldn't have a problem with it. See you, Attila
Am Thu, 18 Feb 2010 22:52:37 +0100 schrieb Attila <vodoo0904@sonnenkinder.org>:
That is true and every example was a good example. But there is a little risk that you got lazy if you don't document what you have done and than including a complete directory with a lot of files could end in a bugreport where people search a longer time because no one is thinking that it was "simple mistake". That is all what i want to say and myself wouldn't have a problem with it.
Why? I doubt it. 1. The wildcard * is a standard on every shell at least in bash. So everybody should know its meaning and what it does. Of course there should be posted a news message that this feature is added to pacman. 2. What will happen if someone will use it accidentally wrong? Nothing except, that there will be many .pacnew files in this directory which can simply be renamed. So there won't be any serious bug. Greetings, Heiko
At Donnerstag, 18. Februar 2010 23:29 Heiko Baums wrote:
2. What will happen if someone will use it accidentally wrong? Nothing except, that there will be many .pacnew files in this directory which can simply be renamed. So there won't be any serious bug.
Oh, so if someone use 'usr/lib/*' than the lib of every new or updated package will get installed with the '.pacnew' ending? Than there is no risk that is true and i'm wrong. Sorry for thinking too much complicated in this case. See you, Attila
Am Fri, 19 Feb 2010 06:51:40 +0100 schrieb Attila <vodoo0904@sonnenkinder.org>:
Oh, so if someone use 'usr/lib/*' than the lib of every new or updated package will get installed with the '.pacnew' ending?
Right, that's what NoUpgrade in pacman.conf does. ;-) Greetings, Heiko
At Freitag, 19. Februar 2010 12:01 Heiko Baums wrote:
Right, that's what NoUpgrade in pacman.conf does. ;-)
Thanks for the smiley at the end because i was very silly (oder anderes gesagt die Leitung auf der ich stand ging mindestens zweimal um die Erde -) ). See you, Attila
participants (9)
-
Aaron Griffin
-
Attila
-
clemens fischer
-
Dan McGee
-
Gerardo Exequiel Pozzi
-
Heiko Baums
-
Pierre Chapuis
-
Ray Kohler
-
Ray Rashif