The only attribute we need in IDistribution is the
pendingremovalduration, which could also defaults to a zope config value.
'root' sounds like a machine dependendent value to me and should fit in
the zope config as well, local_archive_path.
Maybe we still need to handle specific publication paths fo each
distribuiton (mirroring and permission issues), so, I'd not mind to have
an IDistribution.archive_path, which would be joined with
local_archive_path to build former 'root'.
And then a set of path.join s for poolroot, distroot, overrideroot,
cacheroot and miscroot, which could also be provided as properties in
IDistribution. I can't see any use-case for customized cache/misc/pool.
And the IDistroRelease.lucilleconfig:
[publishing]
components = main restricted universe multiverse
Isn't it the same as IDistroRelease.components() ?
Daniel Silverstone wrote:
> The configuration is per distribution and per distrorelease. We should
> not expect it to be in the launchpad.conf
Gina already does it, however I agree that gina works in a more distrorelease.
controlled environment than the distro/
> By all means make it an XML configuration blob which its in the column
> in the DB.
XML & config represent the same issue, I don't think people would be
able to edit/fine-tune it in place.
> Alternatively we can just use proper columns instead of a nasty text
> field.
Could be, but anyway we don't need that bunch of attributes in the DB.
See an example of IDistribution. lucilleconfig
[publishing] uration= 5 tmp/archive /var/tmp/ archive/ ubuntutest /var/tmp/ archive/ ubuntutest/ pool /var/tmp/ archive/ ubuntutest/ dists /var/tmp/ archive/ ubuntutest- overrides /var/tmp/ archive/ ubuntutest- cache /var/tmp/ archive/ ubuntutest- misc
pendingremovald
root=/var/
archiveroot=
poolroot=
distsroot=
overrideroot=
cacheroot=
miscroot=
The only attribute we need in IDistribution is the uration, which could also defaults to a zope config value.
pendingremovald
'root' sounds like a machine dependendent value to me and should fit in
the zope config as well, local_archive_path.
Maybe we still need to handle specific publication paths fo each archive_ path, which would be joined with
distribuiton (mirroring and permission issues), so, I'd not mind to have
an IDistribution.
local_archive_path to build former 'root'.
And then a set of path.join s for poolroot, distroot, overrideroot,
cacheroot and miscroot, which could also be provided as properties in
IDistribution. I can't see any use-case for customized cache/misc/pool.
And the IDistroRelease. lucilleconfig:
[publishing]
components = main restricted universe multiverse
Isn't it the same as IDistroRelease. components( ) ?
[] www.canonical. com
--
Celso Providelo <email address hidden>
Canonical Ltd - http://