[csw-maintainers] Preview of the new mirror structure available
dam at opencsw.org
Sun Nov 8 11:23:56 CET 2009
Am 07.11.2009 um 12:45 schrieb James Lee:
> On 05/11/09, 16:16:42, Dagobert Michelsen wrote regarding
> [csw-maintainers] Preview of the new mirror structure available:
> Is this a preview or a proposal?
A preview of the proposal ;-)
>> pkgs/ (confined to this directory)
>> mytest.pkg.gz (hardlinked to pkgs/mytest.pkg.gz)
> Too complex and risky to be of any use to *users*.
Why "too complex"? The users just subscribe to a URL. The structure
matter as long as they use pkg-get or pkgutil. Apart from that I think
it easier than the current layout as it puts testing/ closed to
> This looks as if your proposal is to formalise the retention of all
> packages and catalogues (a collection's state). At first this seems
> like a good idea but think deeper and you will see that if all
> catalogues are kept there is no way of knowing which are erroneous,
> hence they all become useless. Actually there is a way of knowing
> because we keep the known good sets as stable releases which is
> already handled.
My intentions are different. I want to solve two problems with it:
1. There is no official archive for all released package versions
This is currently handled by http://csw.informatik.uni-erlangen.de/oldpkgs/
While I think that Michael is doing a great job I would prefer that the
project itself would keep an archive. allpkgs/ is my proposal to handle
2. When you install a package you are forced to upgrade other packages
The larger customers of ours have own mirrors from where they install.
However, the smaller installation just subscribe to current/. When an
inexperienced admin just wants to add a package and by error updates
the catalog there is no way other then to update the dependencies of
the package to be installed as there is neither an unchanged location
for scubscription nor the old archived catalog. The freezes are not
meant as replacement for stable, but as substitute to subscribe to
in addition to current/.
>> pkg.tar.gz (also hardlinked from allpkgs)
>> pkg.tar.gz (hardlinked from allpkgs)
>> pkg.tar.gz (symlinked to 5.8, same as in current/)
> This misunderstands the WIP nature of the snapshot process. The
> is on unstable, it's not an entity it's unstable itself that is
Again: This has nothing to do with freezes needed to build stable.
This whole rework of the layout is the result of the discussion we
had on the founding meeting a year ago. I am just a bit slow...
> ** TBD: experimental/ should be filled with the subdirectories from
>> what is now in testing/.
>> Subdirectories can be created by each maintainer and for each
>> folder a subproject
>> is created in experimental which can be synced to separately.
>> ** TBD: packages/ can the go from experimental/ to testing/ when no
>> open issues persist.
> How will you define "no open issues persist"?
That the maintainer of the packages doesn't know of any. Currently
contains packages for which the maintainers _know_ that some things
work but wants to test other things anyway. While it is useful to pkg-
from the testing-catalog it may not be useful for general testing.
That's why I want to confine these specific-things-only testing to
subdirs of experimental/ the maintainers can create at will and use
they think is good but restrict testing/ to packages that are good for
testing by anyone who wants to help testing and every encountered issue
is an unknown, actual bug.
>> This can be used to drive servers. Only packages proven there can
>> go to current/. See
>> for details.
> Here you draw parity to the Debian system. Previous discussion
> the levels you show are not correct.
> "How stuff gets in there", conceptually and practically it doesn't
> because stable is a modified clone of another state done as an atomic
> I feel we've lost sight of the aims of the proposal.
It is a writedown of the discussion of Oslo. If you actually use
another tool to moves packages there is up to you. If they are
released atomically as a whole this is independent of the tool to move
packages between catalogs. The core of the discussion was to formalize
the moving of packages between catalogs, being the one from current to
stable just an example. The important point is to have an API for tools
to deliver to experimental/ and to move from experimental/ to testing/.
More information about the maintainers