Interactive .install?

kleptophobiac · 2005-07-02 14:58:51

I maintain the ABS package ivtv, and I would like to implement a case/esac pair that depends on user input in the ivtv.install file. The reason is that there are two types of firmware available for these cards, and while both sets of cards will work off of one type of firmware, you can get better performance by using the correct firmware.

I was hoping to have a choice that makes symlinks. Is that possible?

I tried putting one in the .install file, but the script doesn't hold the command line, and so the program exists prematurely.

cactus · 2005-07-02 16:25:36

interaction in a .install, or pkgbuild, is generally a bad thing. I think it would be better to set a variable in the pkgbuild that the user can change. Just make sure to prepend an underscore to it so it will not conflict with any other pacman/makepkg variables.

_FOO="bar"
echo $_FOO

kleptophobiac · 2005-07-02 17:29:28

I figured it was... but having to edit the pkgbuild to get the best possible install seems a little unfriendly.

cactus · 2005-07-02 17:31:39

the best solution would likely be to have a seperate pkgbuild for each firmware, then.

iphitus · 2005-07-03 00:06:49

how about you make hte script look in /sys and detect the different devices?

cactus · 2005-07-03 00:36:04

that works fine for the person funning makepkg on their own system, but does nothing for binary ditribution.

That is one issue with pkgbuilds requiring user input and reading info off the system. They work great for interaction on one person's system, but if someone else just tries to install the binary that results from it..bonk!

Dusty · 2005-07-03 01:07:06

Yeah, PKGBUILDs are meant for batch building, not as custom scripts. In a single case its all right, but for distribution, I'd suggest multiple PKGBUILDs with conflicts and provides properly set.

Dusty

iphitus · 2005-07-03 02:24:50

I mean detect in the post install. the post install is the script run on everyone's computer after the package is installed. so if the detection is in there, it would get the appropriate one for that system.

but yeah, seperate packages might be the best way.

cactus · 2005-07-03 02:35:18

iphitus wrote:

I mean detect in the post install. the post install is the script run on everyone's computer after the package is installed. so if the detection is in there, it would get the appropriate one for that system.

aha. Thanks for the clarification iphitus, that does make a bit more sense. I was assuming you meant detection in the pkgbuild itself..

Arch Linux

#1 2005-07-02 14:58:51

Interactive .install?

#2 2005-07-02 16:25:36

Re: Interactive .install?

#3 2005-07-02 17:29:28

Re: Interactive .install?

#4 2005-07-02 17:31:39

Re: Interactive .install?

#5 2005-07-03 00:06:49

Re: Interactive .install?

#6 2005-07-03 00:36:04

Re: Interactive .install?

#7 2005-07-03 01:07:06

Re: Interactive .install?

#8 2005-07-03 02:24:50

Re: Interactive .install?

#9 2005-07-03 02:35:18

Re: Interactive .install?

Board footer