prt-get footprint mismatch ask-option?
Hi, when I do a bigger prt-get action (like sysup) and a footprint mismatch occurs, the command exits. Often I don't notice it and when I look for my prt-get to see whether it has finished, I see, that it had stopped after the first package or something like this :-( I think the footprint checking is a good thing, but I also think, it would be better to handle it different. Exit on mismatch or use -if are both not really the best solution I think. My preferred solution would be to have a beep when a footprint mismatch is recognized with a continue y/n question to decide what to do. My question is: Is their a way to do this or something similar with the current program or, if not the case, does the crux community would like to have such a feature. If so, I would try to dig a bit into the source and try to integrate it and request the maintainers of the program to include my patch. Sebastian
On 17/03/13 19:50, me@sebastian-bechtel.info wrote:
Hi,
when I do a bigger prt-get action (like sysup) and a footprint mismatch occurs, the command exits. Often I don't notice it and when I look for my prt-get to see whether it has finished, I see, that it had stopped after the first package or something like this :-(
I think the footprint checking is a good thing, but I also think, it would be better to handle it different. Exit on mismatch or use -if are both not really the best solution I think.
My preferred solution would be to have a beep when a footprint mismatch is recognized with a continue y/n question to decide what to do.
My question is: Is their a way to do this or something similar with the current program or, if not the case, does the crux community would like to have such a feature. If so, I would try to dig a bit into the source and try to integrate it and request the maintainers of the program to include my patch.
Sebastian
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
Hi, This is why ignore new was implemented. /etc/pkgmk.conf PKGMK_IGNORE_NEW="yes" Or I prefer to do: /etc/prt-get.conf makecommand pkgmk -in In the later case you have to update the footprint with pkgmk but if you use prt-get it'll ignore any new files and only error on missing files. Regards, Danny Rawlins
Quoting Danny Rawlins <d.rawlins@datafast.net.au>:
On 17/03/13 19:50, me@sebastian-bechtel.info wrote:
Hi,
when I do a bigger prt-get action (like sysup) and a footprint mismatch occurs, the command exits. Often I don't notice it and when I look for my prt-get to see whether it has finished, I see, that it had stopped after the first package or something like this :-(
I think the footprint checking is a good thing, but I also think, it would be better to handle it different. Exit on mismatch or use -if are both not really the best solution I think.
My preferred solution would be to have a beep when a footprint mismatch is recognized with a continue y/n question to decide what to do.
My question is: Is their a way to do this or something similar with the current program or, if not the case, does the crux community would like to have such a feature. If so, I would try to dig a bit into the source and try to integrate it and request the maintainers of the program to include my patch.
Sebastian
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
Hi,
This is why ignore new was implemented.
/etc/pkgmk.conf PKGMK_IGNORE_NEW="yes"
Or I prefer to do:
/etc/prt-get.conf makecommand pkgmk -in
In the later case you have to update the footprint with pkgmk but if you use prt-get it'll ignore any new files and only error on missing files.
Regards, Danny Rawlins
Thanks, that's what I was looking for! I just looked in the man page of prt-get and not in prt-get.conf. My mistake. Sebastian
On Sun, Mar 17, 2013 at 09:50:21AM +0100, me@sebastian-bechtel.info wrote:
Hi,
Hello Sebastian,
when I do a bigger prt-get action (like sysup) and a footprint mismatch occurs, the command exits. Often I don't notice it and when I look for my prt-get to see whether it has finished, I see, that it had stopped after the first package or something like this :-(
I think the footprint checking is a good thing, but I also think, it would be better to handle it different. Exit on mismatch or use -if are both not really the best solution I think.
My preferred solution would be to have a beep when a footprint mismatch is recognized with a continue y/n question to decide what to do.
Interactive features are out of question for pkgmk, but -in resp. --ignore-new is probably what you are looking for. HTH and best regards Juergen
Hi Sebastian, On Sun, Mar 17, 2013 at 9:50 AM, <me@sebastian-bechtel.info> wrote:
Hi,
when I do a bigger prt-get action (like sysup) and a footprint mismatch occurs, the command exits. Often I don't notice it and when I look for my prt-get to see whether it has finished, I see, that it had stopped after the first package or something like this :-(
I think the footprint checking is a good thing, but I also think, it would be better to handle it different. Exit on mismatch or use -if are both not really the best solution I think.
My preferred solution would be to have a beep when a footprint mismatch is recognized with a continue y/n question to decide what to do.
I think Danny and Jürgen already covered a better way to cope with the problem you see, however if you still feel playing with your idea of having an interactive prompt you can easily do that by writing a wrapper for pkgmk, checking for the error code indicating a footprint mismatch, and then asking the user what to do. You can then configure prt-get to use your wrapper as 'makecommand' as shown in Danny's mail. This way, you can have the behaviour you want without changing any of the existing tools. HTH, Johannes -- Johannes Winkelmann jw@smts.ch
participants (4)
-
Danny Rawlins -
Johannes Winkelmann -
Juergen Daubert -
me＠sebastian-bechtel.info