[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde
Subject:    Udates to Beta 1 available
From:       "R. Benjamin Hochstedler" <hochstrb () cs ! rose-hulman ! edu>
Date:       1997-10-22 7:28:05
[Download RAW message or body]


-----BEGIN PGP SIGNED MESSAGE-----

Martin,

I appreciate there being someone on the KDE team that is building
RPMs.  Thanks for the good work.  I have a couple of comments.

> ftp://ftp.kde.org/pub/kde/stable/Beta1/distribution/rpm/binary/kdelibs-Beta1-2.rpm
> 
> kcc modules not found problem fixed:
> ftp://ftp.kde.org/pub/kde/stable/Beta1/distribution/rpm/binary/kdebase-Beta1-2.i386.rpm
> ftp://ftp.kde.org/pub/kde/stable/Beta1/distribution/source/kdebase-Beta1-2.src.rpm
> ftp://ftp.kde.org/pub/kde/stable/Beta1/distribution/tgz/binary/kdebase-Beta1-2.bin.tgz
> 
> I also updated the stuff on sunsite.unc.edu and ftp.redhat.com

I think the standard naming convention would be:
kdelibs-1.0b1-1.i386.rpm.  The way you have it, I can't tell which
release the beta testing is being done on.  I think Netscape does it
the way I suggested for their software.  When it goes to the second
beta release, it would be: kdelibs-1.0b2-1.i386.rpm.  If you keep with
your current naming convention, rpm can't tell when you do an update
for kdelibs-Beta2-1.i386.rpm that it's supposed to replase
kdelibs-Beta1-2.i386.rpm.

Also, I think it would be okay to package up each application in its
own package.  I see that in the original set of rpms, you created your 
own subgroup under X11 for KDE (I think it would be simpler if you
named the group "KDE" instead of "K Desktop Environment").  Since you
have subgroups for it anyway, if you use glint to install packages,
all the KDE packages would already be grouped together, so there would 
be no need to pre-group them up into packages.  Since all the packages 
would start with the letter k anyway, when look at the contrib
directory on redhat's site, you can see them all grouped together that 
way.  Another benifit of having a one-to-one correlation with k-apps
and rpms is that when one k-app is updated, you don't have to
repackage the would group and download the whole group.  Some of these 
groups are over 1MB.  That's just too big.

- -Ben

- -- 
R. Benjamin Hochstedler                  Rose-Hulman Institute of Technology
hochstrb@cs.rose-hulman.edu         http://www.cs.rose-hulman.edu/~hochstrb/
1024/8E076DA5 fingerprint = 20 A4 9B 07 F3 9C 0A D9  1F 22 DE EB 82 86 2C 70

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv

iQCVAwUBNE3xVgIO6qiOB22lAQGEYAQA60IAGDgB40Dj6WheqcWnAyJuf4v++xyv
KVAOYp6lP/l4DxGdPl+Tk615H1P1IFhr5/ILvhZAesvbf4IU4yw467PKP+Ex2JoF
VqvQ6+kyO9+VpNmSwoCU9wYhIIUTtRJXx60Ki5UFAoF2S2oAofK5UZGhmVYjJPDb
p2IsnVRAl7o=
=h+ZR
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]