graysky wrote:You can either echo the needed lines with instructions to include manually in a post_install section of readme.install or if too large, you can simply include them in /usr/share/pkgname/foo with instructions for the user to merge them in his/her .bashrc in the same scriptet.
This is the way to go, if you want to upload it to the AUR. The majority of users will hate you for everything else.
If you say so, I will take this advice from expirienced users like you. Thank you
]]>You can either echo the needed lines with instructions to include manually in a post_install section of readme.install or if too large, you can simply include them in /usr/share/pkgname/foo with instructions for the user to merge them in his/her .bashrc in the same scriptet.
This is the way to go, if you want to upload it to the AUR. The majority of users will hate you for everything else.
I just need to add a environmental variable and add something to PATH
Even the JRE package only informs you about a possibly missing PATH item. In my opinion, pacman has no business altering anything on the user side.
]]>I'm creating my first package for AUR. After installation the package needs some changes in .bashrc in order to work.
Where is the best place to do these changes?
Of course I could it in any function of the PKGBUILD. But I think this would brake some conventions, wouldnt it?
Thank you.