Hi Vincent,
Thanks for setting up a yum repository on fossology.org. However,
there is a problem with mixing both i366 and x86-64 in the same
directory. Yum will install BOTH unless you very specifically request
one. For example, you have:
rpms/1.1.0/centos/4/
which contains both .i386.rpm and .x86-64.rpm.
Another problem with your directory hierarchy is that it requires
users to change their yum conf file every time we come out with a new
release. We don't want to do that.
After listening to Bryan Gartner (LinuxCOE) and Jeff Sheltren (OSUOSL)
I think we should use the following the following directory hierarchy
(which will solve the above problems). There should be 2 top level
directories:
rpms/
rpms-testing/
Below this we add the distro, distro version, and architecture (or
SRPMS).
For our current rpms, this means we would end up with the following
directories. For example:
rpms/CentOS/4/i368/
rpms/CentOS/4/x86-64
rpms/CentOS/4/SRPMS
same for CentOS/5, RHEL/4, and RHEL/5.
This way, for example, the CentOS/4/i386/ would contain ALL the
fossology released versions for that distro and arch. That is, rpms/
CentOS/4/i386/ would contain:
fossology-1.1.centos4.i386.rpm
fossology-1.2.centos4.i386.rpm
etc.
With this model, users will not have to update their yum config file
with each fossology release and we won't get caught by someone
inadvertently installing both the i386 and x86-64 versions. When
people install fossology, they will get the latest version unless they
specifically specify an older one.
We might also want a staging area for rpm's so that the rpms are
available on the web, but not in the yum repository. This can be used
for making early test releases, or just a place to put releases before
they are "official". For now, don't worry about this staging area.
It needs a bit more thought.
Could you please use createrepo -p so that the xml files are human
readable. Not that I expect anyone will look at the files much, but
this costs nothing and will save us some time if we do need to look
through the files.
Are you generating GPG signatures?
We can deliver the following file, "fossology.repo" (CentOS shown for
example). Our install can append it to yum.conf or can be installed
in /etc/yum.repos.d. It will only need to be done once, not for each
release.
----------- file: fossology.repo ---------
# FOSSology releases
[fossology]
name=Fossology releases
baseurl=http://fossology.org/rpms/CentOS/$releasever/$basearch
enabled=1
gpgcheck=0
# FOSSology release candidates and other special builds
[fossology-testing]
name=Fossology testing
baseurl=http://fossology.org/rpms-testing/CentOS/$releasever/$basearch
enabled=0
gpgcheck=0
----------- file: fossology.repo ---------
What do you think?
Bob Gobeille
_______________________________________________
fossology mailing list
[email protected]
http://fossology.org/mailman/listinfo/fossology
