[csw-users] Modifying package

Etienne-Hugues Fortin efortin at cyberspicace.com
Tue Apr 26 19:02:21 CEST 2005

Hi Cory,

Tell me more about your package of config file.  Is there any example that I can look at of what you're referring to?  It may be the answer to my request.  What I want is to be able to upgrade easily any installation without having to reapply the minor modification that I made to the config (using simple switch as mod_ssl yes, mod_perl no and so on).

If that's what you are able to do with your solution, I really want to use that solution.

Thank you.


-----Original Message-----
From: users-bounces at lists.blastwave.org on behalf of Cory Omand
Sent: Tue 4/26/2005 11:52 AM
To: questions and discussions
Subject: Re: [csw-users] Modifying package
On Tue, 2005-04-26 at 07:19, Etienne-Hugues Fortin wrote:
> Hi,
> I'm looking at Blastwave right now and I'm unable to find answer about > a specific aspect of it.  I understand that I can install binary > package for a whole bunch of apps.  However, I can't see how I can > customize these apps to my needs.  For example, let say I want to > install Apache or Squid and modify some of the default config (adding > a mod_ or changing the default value of a switch), how do I proceed?  > I've done that on Fedora Core 2 with apt-get where we basically get > the src package, modify the spec file and then, rebuild it but is that > the same with Blastwave?  I didn't see any info about this.


In my own installations, I provide custom configuration files in a
separate package, with one package package per application, or a
"personality" package with configurations for multiple applications
based on the server role (e.g. web server config package which
installs apache/squid conf files plus some monitoring plugins I
wrote).  This package is usually installed in one of the final
stages of a Jumpstart install.  Using a configuration file package,
you can either replace the existing squid and apache configurations
altogether, or you can modify them using sed scripts.

Of course, if a separate package is not desirable, there is nothing
stopping you from:

pkg-get -d blastwave_package
gunzip blastwave_package.pkg.gz
pkgadd -s /tmp/spool -d blastwave_package.pkg

Then you can edit anything you need to and repackage.  Going this
route means you'd need to create a new custom package every time a
new version of the application is released.


Cory Omand <comand at blastwave.org>

users mailing list
users at lists.blastwave.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 3830 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/users/attachments/20050426/568dea3e/attachment-0001.bin>

More information about the users mailing list