-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> This has now been updated to print a warning that it is ignoring
> --stayondomain if --stayonhost is also specified.
Further testing shows that you need yet another conditional, because
- --stayondomain is overridden by --staybelow as well. Personally, I'm of the
opinion that --stayondomain should override any other settings, not the
reverse. The idea is to get working content, not broken content, or at the
very least, print a warning:
"Warning, your use of stayondomain is being overridden by your use
of the stayonhost and staybelow directives"
..or some such.
I think we all need to come to a concensus as to what the precedence
will be, since we all have our own spiders and tools we use to fetch, but we
(mostly) rely on the stock home.html and plucker.ini and ~/.pluckerrc files.
I think it should be as below:
--staybelow = ${url}
--stayonhost # overrides staybelow
--stayondomain # overrides stayonhost _and_ staybelow
This places the precedence in the order most-restrictive to least.
d.
perldoc -qa.j | perl -lpe '($_)=m("(.*)")'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.1.92 (GNU/Linux)
iD8DBQE9mKc8kRQERnB1rkoRAvJbAJoDp/PDVC8fZXv4+FgL/giqRqXiFQCgoZrQ
LlQde6oDRiuQ7s9ibbMnQvU=
=VMPK
-----END PGP SIGNATURE-----
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
