On 13 Jul 2001, Thayne Harbaugh wrote:
> I still feel very strongly about having a tight integration between the
> individual libraries and the files that package them - I thingk it will
> be encorage and improve maintainability.  The spec file doesn't have to
> be in a sub-directory but could go in ggi-core/libgii directly (similar
> for all libs in CVS).

"the" spec file?  Is there to be only one per lib?  I have seen before
packages where there is a specfile alongside every Makefile.

> If my suggestion is rejected I'll be sad =(

These are my main concerns; if we can work out something that keeps
us both somewhat happy, let us try:

1) Make sure that we do not make it harder for a distro 
maintainer who does not have/want CVS access to write new 
packaging scripts by putting things in their way.

2) If another RedHat based distribution wanted it's own customized 
packages, there should be a way for them to be stored in CVS.
E.g. we'd have a distro/redhat and a distro/suse if suse did not
like the way vanilla redhat packaged something.

3) If some distro wants to pre-patch our code in some way that 
we do not want in our mainstream code, these patches should not
clutter up the mainline tree, but we should still be able to keep
them in CVS if we want.

4) distros which want to take one thing from LibGII and one thing
from LibGGI and one thing from LibGGIMISC and put them into the 
same distro-package can still have their distro scripts store in
CVS alongside everyone else's.  I think having all the distros
side by side is good also because it will foster a competitive
spirit between them for packaging.

Some of the above concerns are not likely (but eventually could 
end up being, if rpm improves to include features in more
advanced packaging systems) an issue for RedHat, but I think if we 
have RPMS files in the CVS lib trees and everyone else's in a 
separate CVS tree, we will look like we are playing favorites.

I have no problem with having Makefile targets which will either
copy the distro files in and build, or generate a source tarball 
with the distro files copied in, for any given distro e.g. "make 
suse-dist".  That would be a "maintainer level" makefile rule,
and it is OK for it to know that the RPMS files are all in 
../../distro/redhat.

--
Brian

Reply via email to