summaryrefslogtreecommitdiff
path: root/databases/yasql
AgeCommit message (Collapse)AuthorFilesLines
2022-06-28*: recursive bump for perl 5.36wiz1-2/+2
2021-10-26databases: Replace RMD160 checksums with BLAKE2s checksumsnia1-2/+2
All checksums have been double-checked against existing RMD160 and SHA512 hashes The following distfiles could not be fetched (some may be only fetched conditionally): ./databases/cstore/distinfo D6.data.ros.gz ./databases/cstore/distinfo cstore0.2.tar.gz ./databases/cstore/distinfo data4.tar.gz
2021-10-07databases: Remove SHA1 distfile hashesnia1-2/+1
2021-05-24*: recursive bump for perl 5.34wiz1-2/+2
2020-08-31*: bump PKGREVISION for perl-5.32.wiz1-2/+2
2020-01-26all: migrate some SourceForge homepage URLs back from https to httprillig1-2/+2
https://mail-index.netbsd.org/pkgsrc-changes/2020/01/18/msg205146.html In the above commit, the homepage URLs were migrated from http to https, assuming that SourceForge would use the same host names for both http and https connections. This assumption was wrong. Their documentation at https://sourceforge.net/p/forge/documentation/Custom%20VHOSTs/ states that the https URLs use the domain sourceforge.io instead. To make the homepages from the above commit reachable again, pkglint has been extended to check for reachable homepages. This check is only enabled when the --network command line option is given. Each of the homepages that referred to https://$project.sourceforge.net before was migrated to https://$project.sourceforge.io (27), and if that was not reachable, to the fallback URL http://$project.sourceforge.net (163).
2020-01-18all: migrate several HOMEPAGEs to httpsrillig1-2/+2
pkglint --only "https instead of http" -r -F With manual adjustments afterwards since pkglint 19.4.4 fixed a few indentations in unrelated lines. This mainly affects projects hosted at SourceForce, as well as freedesktop.org, CTAN and GNU.
2019-11-02databases: align variable assignmentsrillig1-2/+2
pkglint -Wall -F --only aligned -r No manual corrections.
2019-08-11Bump PKGREVISIONs for perl 5.30.0wiz1-2/+2
2018-08-22Recursive bump for perl5-5.28.0wiz1-2/+2
2016-07-09Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.wiz1-2/+2
2015-11-03Add SHA512 digests for distfiles for databases categoryagc1-1/+2
Problems found with existing distfiles: distfiles/D6.data.ros.gz distfiles/cstore0.2.tar.gz distfiles/data4.tar.gz distfiles/sphinx-2.2.7-release.tar.gz No changes made to the cstore or mariadb55-client distinfo files. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2015-07-12Comment out dependencies of the stylewiz1-2/+2
{perl>=5.16.6,p5-ExtUtils-ParseXS>=3.15}:../../devel/p5-ExtUtils-ParseXS since pkgsrc enforces the newest perl version anyway, so they should always pick perl, but sometimes (pkg_add) don't due to the design of the {,} syntax. No effective change for the above reason. Ok joerg
2015-06-12Recursive PKGREVISION bump for all packages mentioning 'perl',wiz1-2/+2
having a PKGNAME of p5-*, or depending such a package, for perl-5.22.0.
2014-05-29Bump for perl-5.20.0.wiz1-2/+2
Do it for all packages that * mention perl, or * have a directory name starting with p5-*, or * depend on a package starting with p5- like last time, for 5.18, where this didn't lead to complaints. Let me know if you have any this time.
2013-12-09Fix/Update DEPENDS paterns for perl CORE modules, with some trivial fixes.obache1-3/+3
Bump PKGREVISION for runtime dependency pattern changed packages.
2013-05-31Bump all packages for perl-5.18, thatwiz1-2/+2
a) refer 'perl' in their Makefile, or b) have a directory name of p5-*, or c) have any dependency on any p5-* package Like last time, where this caused no complaints.
2012-10-03Bump all packages that use perl, or depend on a p5-* package, orwiz1-2/+2
are called p5-*. I hope that's all of them.
2012-10-02Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.asau1-3/+1
2009-06-14Remove @dirrm entries from PLISTsjoerg1-2/+1
2008-03-03Mechanical changes to add DESTDIR support to packages that installjlam1-5/+8
their files via a custom do-install target.
2006-07-07Add an explicit run-time dependency on perl because these packagesjlam1-1/+3
install perl scripts. Bump the PKGREVISION for the dependency change.
2006-07-07Reorder sections to more closely follow pkgsrc Makefile guidelines.jlam1-5/+5
2006-07-07Make this package PKGMANDIR-aware.jlam1-3/+3
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2005-12-29Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mkjlam1-2/+1
automatically detects whether we want the pkginstall machinery to be used by the package Makefile.
2005-12-05Ran "pkglint --autofix", which corrected some of the quoting issues inrillig1-2/+2
CONFIGURE_ARGS.
2005-09-28Replaced "# defined" with "yes" in Makefile variables like GNU_CONFIGURE,rillig1-2/+2
NO_BUILD, USE_LIBTOOL.
2005-08-16--prefix is already passed to GNU configure.grant1-2/+1
2005-06-16Create directories before installing files into them.jlam1-1/+3
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 digests in addition to SHA1 ones.agc1-1/+2
2004-04-15Initial import of yasql-1.81 into the NetBSD packages collection.grant4-0/+63
YASQL is an open source Oracle command line interface. YASQL features a much kinder alternative to SQL*Plus's user interface. This is meant to be a complete replacement for SQL*Plus when dealing with ad-hoc queries and general database interfacing. It's main features are: * Full ReadLine support * Alternate output methods * Output of query results * Data Input and Binding * Command pipes * Tab completion * Easy top rownum listings * Enhanced Data Dictionary commands * Query editing * Query chaining * Basic scripting * Config file * Future extensibility