On Mon, Jul 21, 2008 at 11:23 PM, Paul Mattal paul@mattal.com wrote:
Thanks for pointing that out. I changed this to a post_install in dnsmasq 2.43-2, not post_upgrade, since this one you have to read the first time and not thereafter.
This is a problem I've been thinking about for a while. It happens far too often that a message needs to be shown to the user only the first time a package gets upgraded because something important has changed.
Without the need to modify anything we could use the parameters passed to post_upgrade: if the old version is affected by the change (can we use anything like vercmp in install files?) then the message will be shown, otherwise it won't. It's an extra effort on our side, but it helps a lot in cleaning up package installation output. Of course we'll also need to pay attention to when it's time to remove the message.
I have other possible solutions in mind, but they all require changes to pacman or arch, and by far they aren't KISS. Any additional proposal or comment?
Corrado
I don't have a lot to offer as fas as suggestions on implementation, but did want to say that I too find the over use of install messages to be annoying, and it really should only show up on a first installation of the particular version of software it applies too. If it could be referenced later, that would be nice, but it doesn't need to be there every time.
One in particular that stood out for me on a recent upgrade was p7zip's message:
:: In order to use p7zip with mc: :: Add u7z to /usr/share/mc/extfs/extfs.ini :: and add the following to /usr/share/mc/mc.ext: :: :: regex/.(7z|7Z)$ :: View=%view{ascii} 7za l %f :: Open=%cd %p#u7z
I do not have mc installed, nor do I think this should be in an installation message even if I did. If you think it's important, or a good tip for other people, put stuff like that in the wiki. Anyway, that's just my $0.02
-- Aaron "ElasticDog" Schaefer
I think you are wrong. I am using MC, because of old days ;) This message from 7z gave me a new idea! I don't use much p7z (never i think) but a lot MC. If you don't know you don't search for it in a wiki. See, this is education! I like those tool tips :)
On Tue, 29 Jul 2008 14:56:52 -0700, Aaron Schaefer aaron@elasticdog.com wrote:
I don't have a lot to offer as fas as suggestions on implementation, but did want to say that I too find the over use of install messages to be annoying, and it really should only show up on a first installation of the particular version of software it applies too. If it could be referenced later, that would be nice, but it doesn't need to be there every time.
One in particular that stood out for me on a recent upgrade was p7zip's message:
:: In order to use p7zip with mc: :: Add u7z to /usr/share/mc/extfs/extfs.ini :: and add the following to /usr/share/mc/mc.ext: :: :: regex/.(7z|7Z)$ :: View=%view{ascii} 7za l %f :: Open=%cd %p#u7z
I do not have mc installed, nor do I think this should be in an installation message even if I did. If you think it's important, or a good tip for other people, put stuff like that in the wiki. Anyway, that's just my $0.02
-- Aaron "ElasticDog" Schaefer
On Tue, Jul 29, 2008 at 10:58 PM, Amanai amanai@freenet.de wrote:
I think you are wrong. I am using MC, because of old days ;) This message from 7z gave me a new idea! I don't use much p7z (never i think) but a lot MC. If you don't know you don't search for it in a wiki. See, this is education! I like those tool tips :)
On Tue, 29 Jul 2008 14:56:52 -0700, Aaron Schaefer aaron@elasticdog.com wrote:
I don't have a lot to offer as fas as suggestions on implementation, but did want to say that I too find the over use of install messages to be annoying, and it really should only show up on a first installation of the particular version of software it applies too. If it could be referenced later, that would be nice, but it doesn't need to be there every time.
One in particular that stood out for me on a recent upgrade was p7zip's message:
:: In order to use p7zip with mc: :: Add u7z to /usr/share/mc/extfs/extfs.ini :: and add the following to /usr/share/mc/mc.ext: :: :: regex/.(7z|7Z)$ :: View=%view{ascii} 7za l %f :: Open=%cd %p#u7z
I do not have mc installed, nor do I think this should be in an installation message even if I did. If you think it's important, or a good tip for other people, put stuff like that in the wiki. Anyway, that's just my $0.02
-- Aaron "ElasticDog" Schaefer
I too think packages should not give tips like these on post_install messages... maybe there could be a Tips for Packages section in the wiki to list these stuff (which also has the advantage that other people can more easily see/edit/add tips).
Also putting these only in post_install() is IMO sufficient (unless a package upgrade is really going to warrant a redisplay of the msg) Then at least people won't have to see these on every upgrade.
If a package really has to give an install msg which pertains to some other package then it should first check if that package exists (pacman -Q ... is it possible to call pacman from within the post install scripts?), and then print it out.
Le Wed, 30 Jul 2008 03:28:35 +0000, "Abhishek Dasgupta" abhidg@gmail.com a écrit :
If a package really has to give an install msg which pertains to some other package then it should first check if that package exists (pacman -Q ... is it possible to call pacman from within the post install scripts?), and then print it out.
A workaround would be to check if a specific file exists, or if something is in PATH. I use something like that in one of my AUR packages (LTSA) :
which mc > /dev/null 2> /dev/null if [ $? -ne 0 ]; then do_something fi
aur-general@lists.archlinux.org