Syntax :- composer remove VenderName/PackageName

Syntax:- composer remome VenderName/PackageName1

VenderName/PackageName2

If you want to remove more than one package then you have to run this command.

Ex:- composer remove fzaninotto/faker

–dev: It remove packages form require-dev

This means, if it is in require-dev, then you have to remove it from there, then for this, you have to flag the dev.

Ex: composer remove fzaninotto/faker –dev

The post How to Uninstall/Remove Package in Laravel? appeared first on scmGalaxy.

–dev: Add packages to require-dev.

composer require VendorName/PackageName –dev

https://packagist.org/ This is the website, from where you will get Php packages. This is the package repository of Php. You have to open this site, whatever your requirement is, you can do that package.

If you want a viewer with PDF, then you search by typing PDF. Here the first one wants Dompdf / Dompdf, so I clicked on it. After clicking on it, it will show you what is the version tag. And it will also show how to install it. So to install it, you have to type the command composer require dompdf/dompdf.

Before running this command, you should check that the composor.json file which you have is empty. That is, our project is not dependent on anyone. But now we have the requirement of this project so we will run this command.

The post How to Install/Add-Package in Laravel? appeared first on scmGalaxy.

You have to create a composer.joson file and write JSON code yourself with the required properties.

• composer config –global(-g) – Operate on the global config file located at $COMPOSER_HOME/comfig.json by default. Without this option, this command affects the local composer.json file.

• composer config –list (-l) __ It shows all the current config variables.

• composer config setting-key “setting-value” – It sets the config key to the value.

• composer config –unset – It removes the configuration element named by setting-key.

• composer config –editor (-e) – Opens the config file (composer.json) in an editor. Use the –global flag to edit the congif (config.json).

Keys:

• name
• version
• type
• description
• license
• homepage
• keywords

The post How to set up a new or existing package? appeared first on scmGalaxy.

step-1

$ cd project_name

step-2

$ composer update

Step-3

$ composer dump-autoload

After that your problem will be solve. If will not be solve then below commands

Step-4

$ composer require laravel/ui

After that run this commands. you project will be run successfully.

Step-5

$ php artisan serve

The post @php artisan package:discover –ansi handling the post-autoload-dump event returned with error code 255 appeared first on scmGalaxy.

npm install (with no args in a package dir)
npm install <tarball file>
npm install <tarball url>
npm install <folder>
npm install <name> [–save|–save-dev|–save-optional]
npm install <name>@<tag>
npm install <name>@<version>
npm install <name>@<version range>
npm i (with any of the previous argument usage)

This command installs a package, and any packages that it depends on. If the package has a shrinkwrap file, the installation of dependencies will be driven by that. See npm-shrinkwrap(1).

A package is:

a) a folder containing a program described by a package.json file
b) a gzipped tarball containing (a)
c) a url that resolves to (b)
d) a <name>@<version> that is published on the registry with (c)
e) a <name>@<tag> that points to (d)
f) a <name> that has a “latest” tag satisfying (e)
g) a <git remote url> that resolves to (b)

Even if you never publish your package, you can still get a lot of benefits of using npm if you just want to write a node program (a), and perhaps if you also want to be able to easily install it elsewhere after packing it up into a tarball (b).

More info …

https://npmjs.org/doc/install.html

The post npm – Node Packaged Modules appeared first on scmGalaxy.

wget -q -O – pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add –
sudo sh -c ‘echo deb pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list’
sudo apt-get update
sudo apt-get install jenkins

Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post How to add new package to apt-get appeared first on scmGalaxy.

I am kind of new to android build setup. Can you please help me fix the compilation issues as below;

[ERROR] COMPILATION ERROR :
[INFO]
[ERROR] C:\vault\workspace\TREST\QBSharedLib\src\com\intuit\qbsharedlib\quickbooks\common\data\SyncDetails.java:[7,29] package net.sqlcipher.database does not exist
[ERROR] C:\vault\workspace\TREST\QBSharedLib\src\com\intuit\qbsharedlib\quickbooks\common\data\SyncDetails.java:[63,26] cannot find symbol
symbol : class SQLiteDatabase
location: class com.intuit.qbsharedlib.quickbooks.common.data.SyncDetails
[ERROR] C:\vault\workspace\TREST\QBSharedLib\src\com\intuit\qbsharedlib\quickbooks\common\data\SyncDetails.java:[77,32] cannot find symbol
symbol : class SQLiteDatabase
location: class com.intuit.qbsharedlib.quickbooks.common.data.SyncDetails
[ERROR] C:\vault\workspace\TREST\QBSharedLib\src\com\intuit\qbsharedlib\quickbooks\common\data\SyncDetails.java:[90,40] cannot find symbol
symbol : class SQLiteDatabase
location: class com.intuit.qbsharedlib.quickbooks.common.data.SyncDetails
[ERROR] C:\vault\workspace\TREST\QBSharedLib\src\com\intuit\qbsharedlib\quickbooks\common\data\SyncDetails.java:[141,40] cannot find symbol
symbol : class SQLiteDatabase
location: class com.intuit.qbsharedlib.quickbooks.common.data.SyncDetails
[ERROR] C:\vault\workspace\TREST\QBSharedLib\src\com\intuit\qbsharedlib\quickbooks\common\data\QBContentProvider.java:[7,20] package net.sqlcipher does not exist
[ERROR] C:\vault\workspace\TREST\QBSharedLib\src\com\intuit\qbsharedlib\quickbooks\common\data\QBContentProvider.java:[8,29] package net.sqlcipher.database does not exist
[ERROR] C:\vault\workspace\TREST\QBSharedLib\src\com\intuit\qbsharedlib\quickbooks\common\data\QBContentProvider.java:[9,29] package net.sqlcipher.database does not exist
[ERROR] C:\vault\workspace\TREST\QBSharedLib\src\com\intuit\qbsharedlib\quickbooks\common\data\QBDatabaseHelper.java:[6,29] package net.sqlcipher.database does not exist
[ERROR] C:\vault\workspace\TREST\QBSharedLib\src\com\intuit\qbsharedlib\quickbooks\common\data\QBDatabaseHelper.java:[7,29] package net.sqlcipher.database does not exist
[ERROR] C:\vault\workspace\TREST\QBSharedLib\src\com\intuit\qbsharedlib\quickbooks\common\data\QBDatabaseHelper.java:[117,38] cannot find symbol
symbol: class SQLiteOpenHelper
public class QBDatabaseHelper extends SQLiteOpenHelper {

sqlcipher.jar file is located at
dir1/pom.xml
dir1/libs/sqlcipher.jar

-Rajesh
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Package net.sqlcipher.database does not exist appeared first on scmGalaxy.

Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

rajeshkumar replied the topic: the ova package name does not match
Downloaded a OVA file and tried to import it into my VMWare Workstation and if something can go wrong – it does.

“the ova package name does not match the ovf file inside it” was the error message, after some searching I found out that a OVA is nothing else than a compressed tar file with another ending but includes the OVF and VHD files.

Usind 7-zip to look into it I found the name of the OVF and renamed the OVA to the same name – voila – it works
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

rajeshkumar replied the topic: the ova package name does not match
Another way – enterprise.github.com/help/articles/gett…rted-with-virtualbox

Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post The ova package name does not match appeared first on scmGalaxy.

Key Features

* Creation of MSI packages, which can be installed manually on a local PC or automatically on remote PCs through Group Policy or EMCO Remote Installer.
* Intuitive visual editor for managing files, folders, registry and environment installation entries. Truly visual approach – no programming skills required.
* ‘Live Monitoring’ technology that enables capturing of file system and registry changes caused by any application. Collected data used for MSI creation.
* Decompilation, which allows decompiling the existing package, making changes and creating a new customized MSI package.
* Installation of Windows services. Service entries can be defined manually in the visual editor or come from the monitoring results.
* Extended installation management features: system variables support, control of files and registry keys overwriting, file attributes support, files and registry keys permanence options, etc.

The post EMCO MSI Package Builder – Overview appeared first on scmGalaxy.

The post Wise Studio Package 7.0 SP4 appeared first on scmGalaxy.

applicationPackaging replied the topic: Re: Can I nest packages into a package to simplify remote installation via Apple
Iceberg can manage a metapackage and all its components in the same project.

If you need to group existing packages inside a metapackage, Iceberg makes this operation very easy:
1 Open Iceberg.
2 Choose File > New Project… .
3 Select the Core Template > Metapackage template and click Next.
4 Type the name of the project in the Project Name text field and click Finish.
5 Choose View > Components.
6

Drag and drop packages and metapackages that need to be grouped into the Components pane list.
Note: Packages and metapackages can also be dropped in the Packages & metapackages column.
7 Choose Project > Build to build the metapackage.

The post Can I nest packages into a package to simplify remote installation via Apple Rem appeared first on scmGalaxy.

* Wise Package Studio uses the NSAdmin user to run its services. If the password or permissions for this user are changed, WPS may not function properly.
* Since WPS is a per user license, it will only work under the user who installed it. Otherwise, an error about invalid serial numbers will appear when running.
* Batmobile hosts the SQL databases needed by WPS.
o Workbench Database
o Software Manager Database
o Wise Services Database
* The Wise Share Point is located on LSAltiris at c:\Wise Share Point.
* When running the WPS Workbench it prompts for an admin password. It is currently blank.
* We have a license for the web features of the program, but they require .NET 1.1. That version is installed on LSAltiris, but so is .NET 2.0. So, the installer does not see version 1.1 without removing version 2.0 first. Since LSAltiris is already in production, I did not want to uninstall an reinstall .NET.
* If prompted for an admin password when opening up the Workbench, there is no password.

Client Information

There is a virtual machine that acts as a client for the program. This way, we do not have to log into LSAltiris when ever we need to use the software.

* The VM is called Wise Package Client, and its host name wpclient.
* The client works on a per-user base. The client software is currently installed under the NSAdmin account. See the “Notepad” in lscs.byu.edu/utilities for the password.
* The client is really just a shortcut that points to the executables on LSAltiris.

The post Wise Package Studio appeared first on scmGalaxy.

MAGNA INFOTECH one of the premier IT service providers past eleven years. Magna Infotech incorporated in Danbury, CT ÃÆâ€Ãƒâ€šÃ‚¢ÃƒÂ¢Ã¢â‚¬Å¡Ã‚¬Ã¢â‚¬Å“ USA in 1995, started Indian operations in 1997 with head office at Hyderabad and presence in seven locations in India. We have strategic alliances with IT MNC corporate and do provide them our services for their recruitment needs.
>At presents we are 3000 + employee strength and have been closely working with fortune 500 MNC.

I take this opportunity in regards with an exciting opportunity which would bring your career to new heights.

Location: Mumbai
Experience: 4to 8 years
Notice period: 7-10days
Skills: application package developers

.Note:
If you are selected you will be a permanent employee of Magna Infotech.

Revert back with your updated CV in word format with contact details.

If you possess the same and Confident to get into our CMM Level 5 clients all across the Globe, please send across your updated profile to
msridevi@magna.in

Regards,
Sridevi
080- 30041723
Magna Infotech

The post Urgent requirement for Application Package developer appeared first on scmGalaxy.

The post Installation Package Windows Installer appeared first on scmGalaxy.

How to Publish a Nuget package in NuGet Gallery?

Step 1 – Create an account at NuGet.org

Head over to http://nuget.org/ and register for an account. Once you do that, click on “My Account” to see an API Key that was generated for you.

Step 2 – In a command console, run the command:

$ nuget setApiKey Your-API-Key

This will store your API key so that you never need to do this step again on this machine.

Push your package to NuGet Gallery using the command:

$ nuget push YourPackage.nupkg

Reference
https://docs.nuget.org/consume/command-line-reference

The post How to Publish a Nuget package in NuGet Gallery? appeared first on scmGalaxy.

How to create a package in Nuget?

Mehtod 1 – From An Assembly
If you have an assembly, you can easily generate a nuspec file from metadata within the assembly and create a package.

$ nuget spec MyAssembly.dll

This creates a Nuspec file. Edit the NuSpec file as needed and then

$ nuget pack MyAssembly.nuspec

Mehtod 2 – Commands Lines using convention based working directory
Some packages contain more than just assemblies. They may contain

Content and source code that should be injected into the target project.
PowerShell scripts and executables.
Configuration file and source code transformations.

To create a package in this way, you can layout a directory structure that follows the NuGet conventions.

tools – The tools folder of a package is for powershell scripts and programs accessible from the Package Manager Console. After the folder is copied to the target project, it is added to the `$env:Path (PATH) environment variable.
lib – Assemblies (.dll files) in the lib folder are added as assembly references when the package is installed.
content – Files in the content folder are copied to the root of your application when the package is installed.Think of the Content folder as the root of your target application. For example, if I want a package to add an image in the /images directory of the target application, make sure to place the image in the Content/images folder of the package.
build – The build folder of a package is for MSBuild targets files that are automatically inserted into the .csproj file of the application.

Step 1- Create the manifest

$ nuget spec

This will create an XML file with the .nuspec extension.

<?xml version="1.0"?>
   <package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
   <metadata>
   <id>MyPackageId</id>
   <version>1.0</version>
   <authors>philha</authors>
   <owners>philha</owners>
   <licenseUrl>http://LICENSE_URL_HERE_OR_DELETE_THIS_LINE</licenseUrl>
   <projectUrl>http://PROJECT_URL_HERE_OR_DELETE_THIS_LINE</projectUrl>
   <iconUrl>http://ICON_URL_HERE_OR_DELETE_THIS_LINE</iconUrl>
   <requireLicenseAcceptance>false</requireLicenseAcceptance>
   <description>Package description</description>
   <tags>Tag1 Tag2</tags>
   <dependencies>
   <dependency id="SampleDependency" version="1.0" />
   </dependencies>
   </metadata>
 </package>

Edit this file to fill in the values appropriate for your package. Then create the folders needed by your package and copy the correct content in each folder.

$ mkdir lib
   $ mkdir tools
   $ mkdir content
   $ mkdir content\controllers
   $ copy ..\src\SomeController.cs content
   $ copy ..\src\MyLibrary lib
 $ copy ..\src\SomePowershellScript.ps1 tool

With the working directory in place with content, run the following command:
nuget pack YourPackage.nuspec

Mehtod 3 – Using Visual Studio Projects
For simple packages, creating a package from a csproj or vbproj file is a convenient way to create packages. For example, other packages that have been installed into your project will be referenced as dependencies when you create a package this way.

In the folder where the csproj file is, run:

$ nuget spec

This creates a special nuspec file with tokens meant to be replaced at pack time based on the project metadata. For example, $version$ gets replaced by the version specified in the AssemblyVersionAttribute (or AssemblyInformationalVersionAttribute if present) applied to your assembly (typically within the AssemblyInfo.cs file).

These tokens will only be replaced when you execute the pack command with the project file, and not with the nuspec file. The contents of the nuspec file will be located and honored, with the appropriate token replacements executed.

The following is a list of the supported replacement tokens.

Token Source
$id$ The Assembly name
$version$ The assembly version as specified in the assembly’s
AssemblyVersionAttribute (or AssemblyInformationalVersionAttribute if present).
$author$ The company as specified in the AssemblyCompanyAttribute.
$description$ The description as specified in the AssemblyDescriptionAttribute.

You can then edit this nuspec file if you need to customize it. e.g. if you don’t want token replacement for some fields, you hard code them in the nuspec instead.

Also, if you want to pull additional files into the package, you can use a node in the nuspec. e.g. suppose you want to add all the files from some arbitrary other folder into the package, you’d have:

<files>
   <file src="..\..\SomeRoot\**\*.*" target="" /> 
 </files>

You need to run ‘nuget pack’ on the project file, not the nuspec itself. But the nuspec will in fact get picked up. Once your nuspec is ready, you can run:

$ nuget pack MyProject.csproj

If the project references other projects, you can add the referenced projects as part of the package, or as dependencies with -IncludeReferencedProjects option. This is done recursively. For example, suppose you have project A.csproj, which references B.csproj and C.csproj, while B.csproj references D.csproj & E.csproj, C.csproj references F.csproj & G.csproj. Then, when you run

nuget pack A.csproj -IncludeReferencedProjects

the generated package will contain files from projects B, C, D, E, F & G, in addition to files from project A.

If a referenced project has a corresponding nuspec file with the same name, then that referenced project is added as a dependency instead. Using the same example, suppose now there is file C.nuspec in the same directory as project file C.csproj. When you run

$ nuget pack A.csproj -IncludeReferencedProjects

the generated package will contain files from projects B, D, E, in addition to files from project A, and the package has dependency on C.

By default, NuGet will use the default build configuration set in the project file (typically Debug). To pack files from a different build configuration (e.g., Release), you can run:

$ nuget pack MyProject.csproj -Prop Configuration=Release

Reference
https://docs.nuget.org/create/creating-and-publishing-a-package
https://docs.nuget.org/consume/command-line-reference

The post How to create a package in Nuget? | Nuget Tutorial appeared first on scmGalaxy.