Alok, (& question for Darren),
On 10/14/10 00:06, Alok Aggarwal wrote:
In addition to the DTDs being test input files, I think
this project should deliver DTDs into the source tree.
We discussed this a little while back:
http://opensolaris.org/jive/thread.jspa?threadID=133735&tstart=75
OK - here's what I propose:
I will make a new dir in the src repo:
usr/src/lib/install_manifest/dtd/
I will move the 5 DTD files currently under both
cmd/auto-install/*.dtd
and
cmd/distro_const/manifest/*.dtd
to the new dtd dir. These files will be installed in existing dir:
usr/share/install/
as part of the system-library-install pkg and removed from the
install-distribution-constructor and
system-install-auto-install-auto-install-common
pkgs.
I suggest leaving the .xml manifest files under auto-install and
distro_const, as they current are.
Darren, Alok - does that sound OK?
By default, lxml will not fetch any entities (files, DTDs, XIncluded
files, etc) that required network access. This was discussed during my
design review and it was agreed to not override this, for security
reasons.
Not talking about overriding here. If the specified DTD is
an internet URL and validation is requested, I'm assuming
the validation does occur against the DTD on the internet.
Is that correct?
Correct - this will work. However, if, for example, your manifest has
an XInclude link to an external document, this will fail with, eg:
XIncludeError: Attempt to load network entity
http://your.domain.com/path/to/included/file.xml
[I think this, along with before-or-after validation with XInclude,
is another area where I will try to simplify the available options
once we decide how we want to use this functionality.]
If so, is there a way to traverse through http proxies?
Yes - this seems to work OK. I tested this as follows:
- in one terminal, run "snoop" and redirect the output to a temp file
- in another terminal, export http_proxy=http://webcache.uk.sun.com:8080
(one of the proxy servers we used to use before DIA)
- run my tests, but with the manifest modified so it gets its DTD remotely:
<!DOCTYPE dc SYSTEM
"http://cr.opensolaris.org/~dermot/test/manifest.dtd";>
- confirm the test passes and examine the snoop output
Result: snoop output clearly shows the DTD being fetched via the proxy, eg:
brokedown -> webcache1-vhost.UK.Sun.COM HTTP GET
http://cr.opensolaris.org/~dermot/test/manifest.dtd HTTP/1.0
system-library-install.mf: I think you need to sync with slim_source
I know I'll need to break out my changes from the other CUD changes
to this file before I push, but I've just included the latest version
from the
cud project gate here to show which pkgs the MP/MW files would be
going into.
Sounds good. Speaking a little selfishly here, please just make sure
that the DTDs do actually get delivered as part of this package :)
Alok
Thanks,
- Dermot
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
