[Pkg-samba-maint] RFC: split fhs.patch in two parts

Christian Perrier bubulle at debian.org
Sat Sep 22 09:36:29 UTC 2007


> We need to describe the patches and why It Is Good for the Samba Team
> to change samba to better fit the FHS. Here I somehat suspect some
> discussions and potentially some disagreements so we'd better have a
> good and clear argumentation. 


First proposal. We only propose the first two patches and keep
fhs.patch (which points the new variables to fhs-compatible locations)
for Debian (at least in the beginning).

I see this as two mails to samba-technical, as follows:

-----------------------------------------------------------------------
fhs-newpaths.patch: [PATCH] Introduce new path variables to prepare for better FHS respect

This patch prepares the sources to better respect FHS.  This introduces
new configurable paths so that fhs-filespaths.patch can associate
files to them.

The point is adding:

- a path for discardable cache data to host files such as
  browse.dat, printers.tbd, <printer>.tdb
- a path for non discardable state data: basically all TDB files
  that may need to be backed up
- a path for shared data: mostly codepage stuff

All these are currently mixed in "libdir" (${prefix}/lib/samba by
default).

The patch keeps these new paths to point to ${prefix}/lib/samba by
default and does therefore not change the software behaviour.

Indeed, alone, it just adds unused variables..:-)

-----------------------------------------------------------------------

-----------------------------------------------------------------------
fhs-filespaths.patch: [PATCH] Associate file locations to newly introduced path variables

This patch switches the sources to use newly introduced variables in
fhs-newpaths.patch.

The point is doing the following associations:

- discardable cache data (browse.dat, printers.tbd, <printer>.tdb...)
  go to cachedir
- non discardable state data (all TDB files that may need to be backed
  up) go to statedir
- shared data (codepage stuff) go to codepagedir

The patch *does not change* the default location for these
directories. So, there is no behaviour change when applying it.

The main change is for samba developers who have to think when dealing
with files that previously pertained to libdir whether they:
- go in cachedir
- go in statedir
- go in codepagedir
- stay in libdir

Of course, newly introduced files in the future will need discussion
about the most appropriate place. That could require changes to the
developers documentation.

-----------------------------------------------------------------------


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-samba-maint/attachments/20070922/6d545cc0/attachment.pgp 


More information about the Pkg-samba-maint mailing list