Hi I am new to rpm packaging and I want to do 2 things. 1. Modify the %PATH variable and add my “/usr/bin/Test folder” to it. This should be done from RPM while installing. It should exist until we uninstall.

2. Need to open a port so that our program can use it to send and receive data. This also should be done from RPM while installing.

Hi Can you explain little bit more on what to write in script in etc/profiles.d? I also want to update environment variable LD_LIBRARY_PATH, how to do that. This is my first time on linux in my whole life.

Thanks Madhukar Gandra -----Original Message----- From: packaging-bounces(a)lists.fedoraproject.org [mailto:packaging-bounces@lists.fedoraproject.org] On Behalf Of Manuel Wolfshant Sent: Wednesday, March 24, 2010 3:27 AM To: Discussion of RPM packaging standards and practices for Fedora Subject: Re: [Fedora-packaging] port opening and PATH modification in rpm spec file MGandra(a)diskeeper.com wrote: > Hi > > I am new to rpm packaging and I want to do 2 things. > > 1. Modify the %PATH variable and add my "/usr/bin/Test folder" to it. > This should be done from RPM while installing. It should exist until > we uninstall. > > add a script in /etc/profiles.d > 2. Need to open a port so that our program can use it to send and > receive data. This also should be done from RPM while installing. > > Add a Readme.Fedora file to your package describing the reasoning and the needs. There are a miriad of ways to manage a local firewall and as sysadmin I would not be happy with a random package messing with my firewall. -- packaging mailing list packaging(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging __________ Information from ESET NOD32 Antivirus, version of virus signature database 4969 (20100323) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4975 (20100325) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- packaging mailing list packaging(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging

Q: Are you sure? >A: Because it reverses the logical flow of conversation. >>Q: Why is top posting frowned upon?

2.       Need to open a port so that our program can use it to send and receive data. This also should be done from RPM while installing.

On 03/24/2010 06:47 AM, Jon Stanley wrote: > 2010/3/23<MGandra(a)diskeeper.com>: > > >> 2. Need to open a port so that our program can use it to send and >> receive data. This also should be done from RPM while installing. >> > Keep in mind that in the Fedora buildsystem, there will be no network > access allowed during the build process - this defeats the purpose of > reproducible builds if you go grab bits during the build process. I > also agree with Manuel, you do not want to mess with iptables during > the install - the chances for breaking something are extremely high. > The general philosophy is that installing an RPM is about laying the bits down on disk. Small modifications to system configuration are permitted such as adding a necessary user id. However installing an RPM should not in most cases start services or turn on features. Think about the case where someone installs a whole bunch of RPM's just to have them available (yes people do this) and it would be surprising to discover their system was now highly modified running all sorts of things, their firewall and other security features silently modified from their expectation, that's not a good thing. Instead it's better for a package to install a setup script and a README which describes what someone needs to do to activate the features in the package. This way modifying the system configuration is an active explicit step performed by the person administering the system.