Forum OpenACS Development: Re: AOLserver et. al. RPMs available

Jade,

the first post in this thread describes how to produce binaries from the source RPMs. For an explanation of how RPMs work I refer you to http://www.rpm.org/ in particular to the book http://www.rpm.org/max-rpm-snapshot/.

Setting up a yum repository is as simple as placing all binary RPMs of a distribution (e.g. FC3) in a single directory and the run `yum-arch $directory' to make the collection a repository.

With a little thinking you setup a directory structure with one directory for each Linux distrubution. See http://servers.linux.com/article.pl?sid=04/07/22/1718242&tid=30 for step by step instructions.

How to do this from file storage requires some thinking. Will files uploaded to file storage be placed directly in the repository's directory? Should a scheduled proc place them there? Should there be some form of testing before they go into the repository? I'd like the community and the OTC to consider these questions and TIP a concensus proposal.

The beauty of source RPMs is that they contain everything needed to build binary RPMs. If you follow the setup as described in the original post and install the source RPM like so: rpm -ivh $RPM -where $RPM is the name/location of the source RPM you like to install- then the contents of the source RPM will be installed in your %_topdir.

Again, I refer you to http://www.rpm.org/ to learn about using/creating RPMs. The topic is too fast to be explained here. In a nutshell though, each source RPM consists of a tarball of the original source code and a spec file with instructions how to compile the source code and where to install the resulting binaries. The RPM package manager does the rest. It will bundle the binaries into a new binary RPM along with dependecy requirements.

To get started I recommend you install the http://www.thecodemill.biz/repository/aolserver-4.0.10-2.src.rpm and inspect the aolserver.spec file while you read all there is to know about RPMs at http://www.rpm.org/.

For now the procedure to maintain these RPMs is to email me patches to their spec file. Once there are several developers actively involved we can think about different ways of organizing maintenance.

I'll be touching on these topics during Fri's Boston OpenACS meeting.