Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages

  
 
  

home | help
Fritzing(1), fritzing(1)
from prototype to product
barcode(6)
draws a random sequence of barcodes for the products you enjoy
comparoob(1)
compare products
cross_product(3), cross_product_f(3)
Calculates the cross product. Allegro game programming library
dot_product(3), dot_product_f(3)
Calculates the dot product. Allegro game programming library
dvdstyler(1)
cross platform DVD authoring system for Video DVD production
fido_dev_info_manifest(3), fido_dev_info_new(3), fido_dev_info_free(3), fido_dev_info_ptr(3), fido_dev_info_path(3), fido_dev_info_product(3), fido_dev_info_vendor(3), fido_dev_info_manufacturer_string(3), fido_dev_info_product_string(3)
FIDO 2 device discovery functions
lis_array_dot(3)
calculate the Hermitian inner product of the vectors
lis_array_dot(3f)
calculate the Hermitian inner product of the vectors
lis_array_matmat(3)
calculate the matrix-matrix product
lis_array_matmat(3f)
calculate the matrix-matrix product
lis_array_matmat_ns(3)
calculate the matrix-matrix product
lis_array_matmat_ns(3f)
calculate the matrix-matrix product
lis_array_matvec(3)
calculate the matrix vector product
lis_array_matvec(3f)
calculate the matrix vector product
lis_array_matvec_ns(3)
calculate the matrix vector product
lis_array_matvec_ns(3f)
calculate the matrix vector product
lis_array_matvect(3)
calculate the matrix vector product
lis_array_matvect(3f)
calculate the matrix vector product
lis_matvec(3)
calculate the matrix vector product
lis_matvec(3f)
calculate the matrix vector product
lis_matvect(3)
calculate the matrix vector product
lis_matvect(3f)
calculate the matrix vector product
lis_vector_dot(3)
calculate the Hermitian inner product of the vectors
lis_vector_dot(3f)
calculate the Hermitian inner product of the vectors
lmms(1)
software for easy music production
meson(1)
a high productivity build system
nps2gps(1)
convert nucleotide-protein sets to ASN.1 genomic product sets
pbmupc(1)
create a Universal Product Code PBM image synopsis
pfstmo_reinhard02(1)
Photographic Tone Reproduction for Digital Images
relprodbddnodeassoc(3)
computes a relational product. man1/alc_origin.1
sc_GrpProductReduce(3), sc::GrpProductReduce<(3)
T >
volpack-LinAlgebra(3), vpIdentity3(3), vpIdentity4(3), vpNormalize3(3), vpMatrixVectorMult4(3), vpMatrixMult4(3), vpCrossProduct(3), vpSolveSystem4(3), vpSetVector3(3), vpSetVector4(3)
linear algebra routines
Apache2::SiteControl::ManagerFactory(3)
An abstract base class to use as a pattern for custom PermissionManager production
BZ::Client::API(3), BZ::Client::API(3)
Abstract base class for the clients of the Bugzilla API. This is an abstract base class for classes like BZ::Client::Product, which are subclassing this one, in order to inherit common functionality
BZ::Client::Product(3), BZ::Client::Product(3)
Client side representation of a product in Bugzilla This class provides methods for accessing and managing products in Bugzilla. Instances of this class are returned by BZ::Client::Product::get
DBIx::Admin::DSNManager(3)
Manage a file of DSNs, for both testing and production
DBIx::Class::Schema::Loader::Optional::Dependencies(3), $class(3)
Optional module dependency specifications (for module authors) EOC #@@ #@@ SYNOPSIS HEADING #@@ push @chunks, <<"EOC"; =head1 SYNOPSIS Somewhere in your build-file (e.g. ExtUtils::MakeMaker's Makefile.PL): ... e$EUMM_ARGS{CONFIGURE_REQUIRES} = { e%{ e$EUMM_ARGS{CONFIGURE_REQUIRES} || {} }, DBIx::Class::Schema::Loader => $distver, }; ... my %DBIC_CONFIG_AND_ORACLE_DEPS = %{ eval { require $class; $class->req_list_for([qw( dbicdump_config rdbms_oracle )]); } || {} }; e$EUMM_ARGS{PREREQ_PM} = { e%DBIC_CONFIG_AND_ORACLE_DEPS, e%{ e$EUMM_ARGS{PREREQ_PM} || {} }, }; ... ExtUtils::MakeMaker::WriteMakefile(e%EUMM_ARGS); Note: The eval protection within the example is due to support for requirements during the configure build phase not being available on a sufficient portion of production installations of Perl. Robust support for such dependency requirements is available in the CPAN installer only since version 1.94_56 first made available for production with perl version 5.12. It is the belief of the current maintainer that support for requirements during the configure build phase will not be sufficiently ubiquitous until the year 2020 at the earliest, hence the extra care demonstrated above. It should also be noted that some 3rd party installers (e.g. cpanminus) do the right thing with configure requirements independent from the versions of perl and CPAN available. EOC #@@ #@@ DESCRIPTION HEADING #@@ push @chunks, <<'EOC'; =head1 DESCRIPTION Some of the less-frequently used features of DBIx::Class::Schema::Loader have external module dependencies on their own. In order not to burden the average user with modules they will never use, these optional dependencies are not included in the base Makefile.PL. Instead an exception with a descriptive message is thrown when a specific feature can't find one or several modules required for its operation. This module is the central holding place for the current list of such dependencies, for DBIx::Class::Schema::Loader core authors, and DBIx::Class::Schema::Loader extension authors alike. Dependencies are organized in groups where each group can list one or more required modules, with an optional minimum version (or 0 for any version). In addition groups prefixed with test_ can specify a set of environment variables, some (or all) of which are marked as required for the group to be considered by req_list_for Each group name (or a combination thereof) can be used in the public methods as described below. EOC #@@ #@@ REQUIREMENT GROUPLIST HEADING #@@ push @chunks, '=head1 CURRENT REQUIREMENT GROUPS'; my $standalone_info; for my $group (sort keys %$dbic_reqs) { my $info = $standalone_info->{$group} ||= $class->_groups_to_reqs($group); next unless ( $info->{modreqs_fully_documented} and ( $info->{augments} or $info->{modreqs} ) ); my $p = $dbic_reqs->{$group}{pod}; push @chunks, ( "=head2 $p->{title}", "=head3 $group", $p->{desc}, =over, ); if ( keys %{ $info->{modreqs}||{} } ) { push @chunks, map { "=item * $_" . ($info->{modreqs}{$_} ? " >= $info->{modreqs}{$_}" : ) } ( sort keys %{ $info->{modreqs} } ) ; } else { push @chunks, =item * No standalone requirements, } push @chunks, =back; for my $ag ( sort keys %{ $info->{augments} || {} } ) { my $ag_info = $standalone_info->{$ag} ||= $class->_groups_to_reqs($ag); my $newreqs = $class->modreq_list_for([ $group, $ag ]); for (keys %$newreqs) { delete $newreqs->{$_} if ( ( defined $info->{modreqs}{$_} and $info->{modreqs}{$_} == $newreqs->{$_} ) or ( defined $ag_info->{modreqs}{$_} and $ag_info->{modreqs}{$_} == $newreqs->{$_} ) ); } if (keys %$newreqs) { push @chunks, ( "Combined with L</$ag> additionally requires:", =over, ( map { "=item * $_" . ($newreqs->{$_} ? " >= $newreqs->{$_}" : ) } ( sort keys %$newreqs ) ), =back, ); } } } #@@ #@@ API DOCUMENTATION HEADING #@@ push @chunks, <<'EOC';
Gantry::Conf::FAQ(3)
Frequently Asked Questions regarding Gantry::Conf "Why should I use Gantry::Conf at all?" 4 Item "Why should I use Gantry::Conf at all?" There are many reasons why we feel Gantry::Conf is helpful both during development and after deployment. The next two entries should hopefully answer this question for you as they outline a few common scenarios programmers and system administrators often face. "How is Gantry::Conf helpful during development?" 4 Item "How is Gantry::Conf helpful during development?" "Easy separation of development configs from production configs" 4 Item "Easy separation of development configs from production configs" Often programmers have a separate development environment from their production environment. By using <shared> blocks and dev instances you can avoid spending any serious time setting up your application in the development environment. Take this configuration example: <shared dev> dbuser nobody dbpass secret dbconn "dbi:Pg:dbname=dev" </shared> <shared production> dbuser apache dbpass secret2 dbconn "dbi:Pg:dbname=production" </shared> <instance app1> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use production </instance> <instance app1-dev> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use dev </instance> By separating out our production and dev database information into shared blocks we can essentially switch between our production and dev environments by simply changing the instance we are using. If you were working on a script this would be a simple matter of running: $ script.pl --instance=app1-dev instead of: $ script.pl --instance=app1 "How is Gatnry::Conf helpful in production?" 4 Item "How is Gatnry::Conf helpful in production?" Gantry::Conf has several advantages in a production environment. First, it provides a single place for all config information, if you commit to it. Even if you don't commit to it for all apps, it still provides control to the installing admin over how and where conf information is stored. For instance, the admin could put the config information directly into /etc/gantry.conf, or into a separate file in /etc/gantry.d. She could even set up a secure web server where all boxes would go to get their conf. The short answer is, Gantry::Conf is flexible and production environments benefit from flexibility. "How do I pass my instance information into my application?" 4 Item "How do I pass my instance information into my application?" There are many possible ways to do this a few of which are: "Command line arguments" 4 Item "Command line arguments" If your application accepts arguments on the command line we suggest adding an --instance option to pass in the instance's name. "PerlSetVar" 4 Item "PerlSetVar" In a mod_perl environment you could use a PerlSetVar, possibly named GantryConfInstance, to pull in this value for your application. "ModPerl::ParamBuilder" 4 Item "ModPerl::ParamBuilder" Again in a mod_perl environment, another option would be to use ModPerl::ParamBuilder to pass the instance name. "Hard coded" 4 Item "Hard coded" We include this for the sake of completeness, but advise against it. You could always simply hard code your instance information into your application, but this will greatly reduce the flexibility you have. "How do I add a different provider for an existing ConfigVia method?" 4 Item "How do I add a different provider for an existing ConfigVia method?" Place your provider module in the Gantry::Conf::Provider::Method::* namespace. Make sure your public API matches the existing providers which use the same method. For instance the flat file providers all implement a config method which is called as a class method and receives a file name. "How do I add to the ConfigVia methods?" 4 Item "How do I add to the ConfigVia methods?" If none of the existing provider methods will do, you need to work in Gantry::Conf. In particular, you need to augment the dispatch hash with the name of your provisioning method and a sub name which will handle it. Then you need to implement the method you put in %dispatch
Geo::EOP(3)
Earth Observation Products EOP
Interchange6::Cart::Product(3)
Cart product class for Interchange6 Shop Machine
JMX::Jmx4Perl::Product::ActiveMQ(3)
Handler for Jonas
JMX::Jmx4Perl::Product::BaseHandler(3)
Base package for product specific handler
JMX::Jmx4Perl::Product::Geronimo(3)
Handler for Geronimo
JMX::Jmx4Perl::Product::Glassfish(3)
Handler for Glassfish
JMX::Jmx4Perl::Product::Hadoop(3)
Handler for Hadoop
JMX::Jmx4Perl::Product::JBoss(3)
Handler for JBoss
JMX::Jmx4Perl::Product::Jetty(3)
Handler for Jetty
JMX::Jmx4Perl::Product::Jonas(3)
Handler for Jonas
JMX::Jmx4Perl::Product::Resin(3)
Handler for Resin
JMX::Jmx4Perl::Product::SpringDM(3)
Handler for Spring dm-Server
JMX::Jmx4Perl::Product::Terracotta(3)
Handler for Terracotta server
JMX::Jmx4Perl::Product::Tomcat(3)
Handler for Apache Tomcat
JMX::Jmx4Perl::Product::Unknown(3)
Fallback handler
JMX::Jmx4Perl::Product::Weblogic(3)
Handler for Oracle WebLogic
JMX::Jmx4Perl::Product::Websphere(3)
Handler for IBM Websphere
Jifty::Manual::Deploying(3)
Deploying your application for production use
Jifty::Manual::Deploying_zhtw(3)
佈署你的應用程式 Deploying your application for production use
MogileFS::Store::SQLite(3)
For-testing-only not-for-production SQLite storage for MogileFS
Mojo::Server::Hypnotoad(3)
A production web serv...ALL GLORY TO THE HYPNOTOAD!
Net::Amazon::Property(3)
Baseclass for products on amazon.com
Net::Amazon::Validate::ItemSearch::de::OfficeProducts(3)
valid search indicies for the de locale and the OfficeProducts SearchIndex
Net::Amazon::Validate::ItemSearch::fr::OfficeProducts(3)
valid search indicies for the fr locale and the OfficeProducts SearchIndex
Net::Amazon::Validate::ItemSearch::uk::OfficeProducts(3)
valid search indicies for the uk locale and the OfficeProducts SearchIndex
Net::Amazon::Validate::ItemSearch::us::OfficeProducts(3)
valid search indicies for the us locale and the OfficeProducts SearchIndex
Paws::EC2::ConfirmProductInstance(3)
Arguments for method ConfirmProductInstance on Paws::EC2
Perl::Critic::Policy::ControlStructures::ProhibitYadaOperator(3)
Never use "..." in production code
Pipeline::Production(3)
wrapper for production objects
STEP(5)
ISO 10303 Standard for the Exchange of Product model data
Set::CrossProduct(3)
work with the cross product of two or more sets
VM::EC2::ProductCode(3)
Object describing an Amazon EC2 product code
attach(1), bk attach(1)
attach a component repository to a product repository
bk-comps(1), bk comps(1)
list the components belonging to a product
cross(1)
output the cross product of two or more sets
r.cross(1), r.cross (1)
Creates a cross product of the category values from multiple raster map layers
home | help