OpenSolaris

Open

Solaris it’s New Version of OS from Sun Microsystems. Inc, it’s based on Solaris 10 OS and it’s ready to be best OS for Desktop and Server’s because it’s Built on Solaris 10 OS and all Solaris Future have it and more application for normal user like Desktop PC and all kind of workstation and have more Driver’s and Application for Usual used like

– Internet Application (firefox, Pidgin, Thunderbird, etc …)

– Office Application (OpenOffice.org and all PDF to create and open)

– Multimedia Application (all kind of codec You need)

– Desktop GNOME it’s Open Source from GNU for Best Desktop from Open Source World

– Developer Tools like (Net Beans, Java, C++, etc…)

And more more of Application from OpenSolaris Repository on the Internet or Download from www.sunfreeware.com

OpenSolaris Project: Arabic Portal

this group work on OpenSolaris and work to translate System Interface for arabic and it’s Part of

internationalization & localization for Translate

and part of OpenSolaris Community

Goals for this Group

* Translate and OpenSolaris and help to redistributed between Arab

* Translate and Correct all application translate

* Help any one He need to work on it

* Discuss and Develop OS as Common Development and Distribution License (CDDL)

and You can Read the FAQ: Common Development and Distribution License (CDDL)

If you have any quary or ‫ proposal you can connect to manage of Project Seba barto with E-mail sebabarto@gmail.com

or to me Hosam Al Ali E-mail a.hosam@gmail.com

and for all Arabic Discuss and all quary About How You join us and work inside this Group and be memeber on

Mailing list for Arabic Group : g11n-ar-discuss@opensolaris.org

====================================================

Creating and publishing SVR4 and IPS packages

How to Create and Publish an IPS Package

There are different types of IPS packages that can be created. A package is a collection of files, directories, drivers, and dependencies in a defined format. This task shows how to create a package that consists of a directory, a file, a dependency, and a name attribute. The package is then published to the repository using the pkgsend command.
Note – This examples publishes the packages to the default repository,
http://localhost:10000. If you are publishing a package to a repository other than the
default repository, ensure that the repository is created and use the -s option with the
pkgsend command to specify the repository. How to create a new repository, read this blog.

---

1. Create a temporary directory on your system.

$ mkdir tmp

2. Change the directory to the temporary directory.

$ cd tmp

3. Create a directory called package.

$ mkdir package

4. Change the directory to package.

$ cd package

5. Create a text file under the directory package.

$ gedit text_file

Note – The files can be of any type. This example uses a text file.

6. Export the directory package. Specify a version number and a sub-version number for the package. In this example, the package has a version number of 0.5.11 and a subversion number of 5.11-0.101. Note the back quotes used in this command.

$ eval ‘pkgsend open package@1.0-1‘

Note – Specify the package name, version number and subversion number correctly. This cannot be changed afterwards.

7. Add attributes to the package. In this task you add a directory action with attributes of mode, owner, group, and path. Path is the key attribute for the directory action and has to be specified.

$ pkgsend add dir mode=0555 owner=root group=bin path=/etc/package

8. Add the file text_file under the package directory.

$ pkgsend add file package/text_file

9. Add attributes to the file. In this example, you add the file action with the attributes of mode, owner, group, and path. Path is the key attribute for the file action and has to be specified.

$ pkgsend add file package/text_file mode=0555 owner=root group=bin
path=/etc/package

Note – Actions can also be included in a file. This file can then be added to the current transaction by using the pkgsend include command.

Note – The path attribute specifies the directory where the file will be created. This path should exist on the IPS client although it can be different from the file’s location on the IPS server.

10. We have now created a package package consisting of a directory and a file.
11. We will add a dependency for this package and set a name attribute.

    $ pkgsend add depend fmri=pkg:/depends_on_this_package@0.5.11,5.11-0.101 type=require
    $ pkgsend add set name=description value="Example Package"

    Note – If the resources have been specified in a file, use the pkgsend include resource_filename command instead of the pkgsend add command, to add the resources to the current transaction.

12. Use the following option to close the transaction.

$ pkgsend close

Creating and Publishing a Simple Package

Example 1

This example uses the pkgsend command to create and publish a package.

$ eval ‘pkgsend open package@0.5.11,5.11-0.101‘
$ pkgsend add file package mode=0555 owner=root group=bin path=/usr bin/package
$ pkgsend close

Example 2

This example shows how to publish installed application nano.

Configure and install nano, e.g. into directory nano. In this directory run:

$ eval `pkgsend open nano@1.0-1`
$ for ITEM in `find .`; do if [ -d "$ITEM" ]; then pkgsend add dir mode=0555 owner=root group=bin path=`echo $ITEM | sed s%\./%%`; else pkgsend add file "$ITEM" mode=0555 owner=root group=bin path=` echo $ITEM | sed s%\./%%`;fi;done
$ pkgsend close

How to Publish SVR4 Packages to Your Repository

SVR4 packages can be installed directly on your system by using the pkgadd and related commands.

SVR4 packages can be published to the IPS repository by using the pkgsend command.

1. Open the transaction.

$ eval ‘pkgsend open svr4pkg‘

2. Include the manifest associated with the SVR4 package.

$ pkgsend include ips-manifest-with-metadata

3. Import the package.

pkgsend import svr4pkg

4. Close the transaction.

pkgsend close