Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Changes:
- The bundled file XML::Node.sgml had been renamed to XML-Node.sgml (windows
friendly?)
- Diff between previous XML::Node.sgml and new XML-Node.sgml:
--- XML-Node-0.10/XML::Node.sgml Mon Nov 15 21:18:52 1999
+++ XML-Node-0.10.new/XML-Node.sgml Fri Jan 5 20:23:46 2001
@@ -69,7 +69,7 @@
$p->register(">Orders>Order","end" => \&handle_order_end);
print "Processing file [orders.xml]...\n";
-$p->parse("orders.xml");
+$p->parsefile("orders.xml");
So...
Bump PKGREVISION, update distinfo and remove previous distfile from
ftp.netbsd.org.
While here use perl5/module.mk and use buildlink2.
|
|
pkgsrc. Instead, a new variable PKGREVISION is invented that can get
bumped independent of DISTNAME and PKGNAME.
Example #1:
DISTNAME= foo-X.Y
PKGREVISION= Z
=> PKGNAME= foo-X.YnbZ
Example #2:
DISTNAME= barthing-X.Y
PKGNAME= bar-X.Y
PKGREVISION= Z
=> PKGNAME= bar=X.YnbZ (!)
On subsequent changes, only PKGREVISION needs to be bumped, no more risk
of getting DISTNAME changed accidentally.
|
|
${PREFIX} -- everything else is pickup up from ${BUILDLINK_DIR}.
|
|
|
|
The automatic truncation in gensolpkg doesn't work for packages which
have the same package name for the first 5-6 chars.
e.g. amanda-server and amanda-client would be named amanda and amanda.
Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for
amanda-server.
All svr4 packages also have a vendor tag, so we have to reserve some chars
for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6
or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the
vendor tag enough room.
All p5-* packages and a few other packages have now a SVR4_PKGNAME.
|
|
|
|
|
|
Slightly different distfile (parse -> parsefile in one place).
|
|
+ move the patch digest/checksum values from files/patch-sum to distinfo
|
|
|
|
|
|
If you are only interested in processing certain nodes in an XML
file, this module can help you simplify your Perl scripts significantly.
The XML::Node module allows you to register callback functions
or variables for any XML node. If you register a call back function,
it will be called when the node of the type you specified are
encountered. If you register a variable, the content of a XML node
will be appended to that variable automatically.
|