license of software package

10 More Discussions You Might Find Interesting

1. Ubuntu

Ubuntu software package compatibility

I don't have internet connection in my Ubuntu server, so package download directly from internet is not possible. So if I download package from Index of /ubuntu How do I find which version of package is compatible with my Release of Ubuntu server ( 15.10 ) user01@ubuntu01:~$ lsb_release -a...

2. Shell Programming and Scripting

Software License Expire in 30 days

I wrote code to read a file text with contents of expiration dates and products. The products expire in thirty days and each day an email message is send as a reminder of the number of days left before the license expires. The code generates errors when executed . Here is part of the code....

3. Red Hat

How to Customize/install software package after?

Hi Team While installation of RHEL, By mistake I have selected "Customize Later". RHEL has installed with basic software. NOw I need to install the other package which is available in DVD, How Can I get the same package selection window to install the software ?

4. Solaris

Liveupgrade. Exclude software package

Hello. Im about to upgrade 6 solaris 10u7 x86 servers with live upgrade. I have done this before succesfully, but this time i would prefer to keep the current java versions from the u7 release. Is there any way to block luupgrde from installing newer packages of java? I looked at the -P...

5. SuSE

update package/software questions

Hi, In SUSE linux, it looks like that I can update the package using YAST or install the package from source. So, which way works better? Also, if i install the package of new version. Do i need to remove/delete the old version package, or I just need to change my environments and keep the old...

6. Solaris

Change hostid for software install - license issue

Hi all. Solaris 9. After I change the hostid, how can I change it back without rebooting the machine? Thanks

7. Shell Programming and Scripting

Convert collection of scripts into a software package

Hi, I have a "package" of BASH shell scripts. This package consists of a master script (where users specify processing variables), and sub-scripts (the master script determines which of these are called, and in which order). These scripts are used to process data related to my field...

8. UNIX for Dummies Questions & Answers

Question on install software package on Linux

Hello ALL, I am not very sure about the following two questions, I have install some packages on my Linux system, though. Q1. Should I log in as root to install a software package on a Linux system? Q2. If I log in as a common user, say 'Mike', and install a software on Mike's home...

9. Solaris

Solaris 10 Software Package Manager

Hi there, maybe one of you knows the software package tool during the installation of solaris 10. You are able to choose an installtion and customize it with pressing F4 .... a very nice list occurs where you can select packages like apache, ssh and so on ... Is it possible to start this...

10. UNIX for Advanced & Expert Users

looking for SSL software package (AIX 5.1)

When i install SSH on AIX 5.1 I get the following message { A prerequisite package has not been installed. Open SSH requires Open SSL (Secure Sockets Layer). Please install Open SSL from the AIX Toolbox for Linux CD or Toolbox website: } I cannot find the AIX toolbox for linux CD, also on...

LEARN ABOUT CENTOS

perl::critic::policy::variables::prohibitpackagevars

Perl::Critic::Policy::Variables::ProhibitPackageVars(3) User Contributed Perl DocumentationPerl::Critic::Policy::Variables::ProhibitPackageVars(3)

NAME

       Perl::Critic::Policy::Variables::ProhibitPackageVars - Eliminate globals declared with "our" or "use vars".

AFFILIATION

       This Policy is part of the core Perl::Critic distribution.

DESCRIPTION

       Conway suggests avoiding package variables completely, because they expose your internals to other packages.  Never use a package variable
       when a lexical variable will suffice.  If your package needs to keep some dynamic state, consider using an object or closures to keep the
       state private.

       This policy assumes that you're using "strict vars" so that naked variable declarations are not package variables by default.  Thus, it
       complains you declare a variable with "our" or "use vars", or if you make reference to variable with a fully-qualified package name.

	   $Some::Package::foo = 1;    # not ok
	   our $foo	       = 1;    # not ok
	   use vars '$foo';	       # not ok
	   $foo = 1;		       # not allowed by 'strict'
	   local $foo = 1;	       # bad taste, but technically ok.
	   use vars '$FOO';	       # ok, because it's ALL CAPS
	   my $foo = 1; 	       # ok

       In practice though, its not really practical to prohibit all package variables.	Common variables like $VERSION and @EXPORT need to be
       global, as do any variables that you want to Export.  To work around this, the Policy overlooks any variables that are in ALL_CAPS.  This
       forces you to put all your exported variables in ALL_CAPS too, which seems to be the usual practice anyway.

CONFIGURATION

       There is room for exceptions.  Some modules, like the core File::Find module, use package variables as their only interface, and others
       like Data::Dumper use package variables as their most common interface.	These module can be specified from your .perlcriticrc file, and
       the policy will ignore them.

	   [Variables::ProhibitPackageVars]
	   packages = Data::Dumper File::Find FindBin Log::Log4perl

       This is the default setting.  Using "packages ="  will override these defaults.

       You can also add packages to the defaults like so:

	   [Variables::ProhibitPackageVars]
	   add_packages = My::Package

       You can add package "main" to the list of packages, but that will only OK variables explicitly in the "main" package.

SEE ALSO

       Perl::Critic::Policy::Variables::ProhibitPunctuationVars

       Perl::Critic::Policy::Variables::ProhibitLocalVars

AUTHOR

       Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>

COPYRIGHT

       Copyright (c) 2005-2011 Imaginative Software Systems.  All rights reserved.

       This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.  The full text of this license
       can be found in the LICENSE file included with this module.

perl v5.16.3							    2014-06-09		   Perl::Critic::Policy::Variables::ProhibitPackageVars(3)

HP-UX