Monday Jul 10, 2006

Solaris Package Companion v0.6



Well, it is time for another update of the Solaris Package Companion. During the course of some additional testing, I found a few bugs which I have corrected in this new version. The biggest issue corrected in this update is the detection of packages versus clusters. I also added a check to avoid an exception case where a package is defined in a clustertoc(4) file but it cannot be found in the distribution (or on the local system when in local-only mode). For those interested, here is a diff:

blackhole$ diff spc-v0.5.ksh spc-v0.6.ksh
44,48c44,45
< BASEDIR=""
< REPOSITORY=""
<
< export BASEDIR REPOSITORY
<
---
> export BASEDIR=""
> export REPOSITORY=""
69c66,69
<    else
---
>    elif [ -d "`dirname ${fileName}`" ]; then
>       # GMB: This is a small hack to avoid generating an error message
>       #      when a package is listed in a "contents" file but it does
>       #      not otherwise exist (e.g., SUNWphx on snv_18)
88a89,94
>    if [ -z "${name}" ]; then
>       # This method should only be trusted when in "local only" mode.
>       if [ ${LOCAL_ONLY} -eq 1 ]; then
>          name="`pkgparam ${1} NAME 2>/dev/null`"
>       fi
>    fi
221c227
<             if [ `echo ${member} | grep -c "\^[A-Z]\*C"` -eq 1 ]; then
---
>             if [ -d ${C_DIR}/${member} ]; then

If you are interested in giving this version a whirl, please download version 0.6 and let me know what you think! Thank you to everyone who has provided feedback and ideas so far! Keep them coming!

Take care,

Glenn

Technorati Tag:

Friday Jun 30, 2006

Solaris Package Companion v0.5



A few days ago, I posted version 0.4 of the Solaris Package Companion. I had a little time today to do some tweaking based on the feedback that I have received so far. Today, I am pleased to announce that I have made version 0.5 available.

There is only two signficiant differences between versions 0.4 and 0.5. In version 0.5, you must specify that you want to create a working repository for the tool using the newly added -i option (which must be used with either the -l (local) or -s (source distribution) options. Once the repository has been created, the rest of the code should operate in the same manner as before.

The second difference is that during the creation of the repository, the tool will collect package names automatically. This way, you do not need to specify either the -l or -s options after the repository has been created. This makes the -v (verbose) mode a bit faster although the repository creation process (a one time event) is just a little bit longer.

You will still need to specify one of those two options if you want to try out the undocumented -f option to map a file name to a package (if possible). This functionality is still in development but feel free to try it out!

I did add a bunch of new exception handling code that should make it easier to know what is going on if there is a problem or if required arguments are not being passed in a way expected by the program. I hope that these updates will make this tool more easy for everyone to use. Please let me know what you think about the changes!

Thank you to everyone who has provided feedback and ideas so far! Keep them coming!

Take care,

Glenn

Technorati Tag:

Thursday Jun 22, 2006

Solaris Package Companion

[Read More]
About

This area of cyberspace is dedicated the goal of raising cybersecurity awareness. This blog will discuss cybersecurity risks, trends, news and best practices with a focus on improving mission assurance.

Search

Archives
« May 2015
SunMonTueWedThuFriSat
     
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
      
Today