Re: Installer-dev Digest, Vol 49, Issue 16
Re: Installer-dev Digest, Vol 49, Issue 16
- Subject: Re: Installer-dev Digest, Vol 49, Issue 16
- From: "OSullivan, Steve" <email@hidden>
- Date: Wed, 24 Sep 2008 09:58:42 -0700
- Thread-topic: Installer-dev Digest, Vol 49, Issue 16
Thanks Ulf,
But no, removing the erroneous 'if' did not change the outcome of the
running of this script. But seriously, thanks for the input (I hadn't seen
that for a couple of (ahem) days....)
SteveO
On 9/24/08 8:58 AM, "email@hidden"
<email@hidden> wrote:
> Send Installer-dev mailing list submissions to
> email@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.apple.com/mailman/listinfo/installer-dev
> or, via email, send a message with subject or body 'help' to
> email@hidden
>
> You can reach the person managing the list at
> email@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Installer-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Permissions on 10.5.4 & packagemaker 2.1.1 (Bill Royds)
> 2. Re: Version control in Installer Packages (Ulf Dunkel)
> 3. Re: Version control in Installer Packages (Ulf Dunkel)
> 4. dylib inter-dependencies, install_name_tool and @loader_path
> (email@hidden)
> 5. Re: dylib inter-dependencies, install_name_tool and
> @loader_path (email@hidden)
> 6. PackageMaker exits with 0, but no installer package is
> created...help! :) (OSullivan, Steve)
> 7. Re: PackageMaker exits with 0, but no installer package is
> created...help! :) (Ulf Dunkel)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 23 Sep 2008 15:02:35 -0400
> From: Bill Royds <email@hidden>
> Subject: Re: Permissions on 10.5.4 & packagemaker 2.1.1
> To: Annette Brooks <email@hidden>
> Cc: "email@hidden" <email@hidden>
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset="windows-1252"
>
>
> On 23-Sep-08, at 13:36 , Annette Brooks wrote:
>
>> I am running on OS 10.5.4. Haven‚t upgraded my Packagemaker to v3
>> because of all of the comments on this forum, so I am still running
>> 2.1.1.
>>
>> When I try to set permissions for files through Edit File
>> Permissions on the Contents tab, I used to see all of the owners and
>> groups that were available to be set on the file ˆ root, wheel,
>> admin, etc. Now I see cryptic information ˆ such as „S-1-5-32-550‰
>> or „ABCDEFAB-CDEF-ABCD-EFAB-CDEF0000005C‰
>>
>> Anyone know where these things are coming from and what to do about
>> it??? _______________________________________________
> d
> If it can't look up account numbers to convert them to names, that is
> what it woul look like.
> The S-1-5-32-550 format is used for Windows accounts, so if you are
> authenticating against Active Directory, that would be the source.
> Similarly the second format looks like UID account numbers.
>
> Have you go a directory server that was unavailable?
>
>
> Bill Royds
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.apple.com/pipermail/installer-dev/attachments/20080923/ba2a6130/a
> ttachment.html
>
> ------------------------------
>
> Message: 2
> Date: Wed, 24 Sep 2008 07:53:07 +0200
> From: Ulf Dunkel <email@hidden>
> Subject: Re: Version control in Installer Packages
> To: Scott Amory <email@hidden>
> Cc: email@hidden
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Scott.
>
>> I'm sorry to say that I think that this is a bug in PackageMaker.
>
> Thank you - I love straight answers. :-)
>
>
>> In your situation I would suggest you manually
>> change the distribution after creating it through PM. And please file a
>> bug for this.
>
> I'll do both of what you suggested. Thank you.
>
> Best regards,
> UlfDunkel
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 24 Sep 2008 08:10:54 +0200
> From: Ulf Dunkel <email@hidden>
> Subject: Re: Version control in Installer Packages
> To: Scott Amory <email@hidden>
> Cc: email@hidden
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>>> In your situation I would suggest you manually change the distribution
>>> after creating it through PM. And please file a bug for this.
>>
>> I'll do both of what you suggested. Thank you.
>
> Talking about "manually change the distribution":
> Do you refer on the file <myPackage>.mpkg/Contents/distribution.dist?
>
> I opened in TextWrangler and found a similar line there in
>
> <script>function pm_volume_check()
>
> Right?
>
> PS: Bug #6242214 filed.
>
> Best regards,
> UlfDunkel
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 24 Sep 2008 11:49:37 -0000 (GMT)
> From: email@hidden
> Subject: dylib inter-dependencies, install_name_tool and @loader_path
> To: email@hidden
> Message-ID: <email@hidden>
> Content-Type: text/plain;charset=UTF-8
>
> Hi folks,
>
> I am trying to make my applications distribution for mac OSX.4 and X.5, but
> have a couple of problem with the dynamic loading of libraries.
>
>
> My first question is:
> install_name_tool allows changing the "id" of a dynamic library, with -id.
> But What Does "id" Mean ?
> And what is the impact of the lib's "id" on loading?
> I've browsed the doc and the Net for long, but did not find any clear info...
>
>
> My second question is:
> What does @loader_path means exactly ?
> I did not find any clear info on this, and basically, the observed
> behavior does not match what the doc (apparently) says.
>
>
>
> Let's now get into a bit more details.
>
>
> My distribution contains various executables, both bundled apps and
> command-line, that rely on various interdependent libraries. The distrib
> looks like:
> distrib
> |_ bin
> |_ cmdlineexecutable
> |_ application.app
> |_ lib
> |_ A.framework
> |_ B.framework
> where both executable depend on A AND B, and where A depends on B.
>
>
> Since the executables are NOT on the same level in the distribution tree,
> using @executable_path inside a library to refer to another library is NOT
> possible.
>
>
> I guess I have to use @loader_path: the executable would refer to a
> libraries using @executable_path, and the libraries would refer to each
> others using @loader_path
>
>
> According to the doc:
>> Library-relative location. To specify a file path relative to
>> the location of the library itself,
>> place the @loader_path macro at the beginning of the pathname.
>
> However, when using @loader_path, and when the framework is installed BOTH
> inside my distribution AND in a system-searchable location (eg:
> /Library/Framework) then BOTH versions of a library are loaded when
> launching the app.
>
>
> I guess that:
> - the executable, that depends on frameworks A and B refered by using
> @executable_path, loads the executable-relative versions of the frameworks
> A and B
> - framework A, that depends on framework B referred by using @loader_path,
> loads the version of B which is located in /Library/Frameworks
>
>
> Hence, @loader_path would NOT refer to the currently-loaded library
> path... And the doc would lie :/
>
>
> I would appreciate any help on this situation.
>
> Thanks much for your attention,
> best-
> Nicolas
>
> PS: First message on this list. I hope it I picked the correct list. Sorry
> if I was wrong :/
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 24 Sep 2008 13:43:50 -0000 (GMT)
> From: email@hidden
> Subject: Re: dylib inter-dependencies, install_name_tool and
> @loader_path
> To: email@hidden
> Message-ID: <email@hidden>
> Content-Type: text/plain;charset=UTF-8
>
> Hi again,
>
> Indeed, one of the problems was caused by a dynamically dylib loaded at
> run time (a plugin). The plugin was searched in a global system scope,
> instead
> of being searched inside my distribution.
>
> Hence, as far as checked, using @loader_path/**relative_path_to_B** inside a
> .dylib A to refer to a dependent library B behave as following:
>
> 1- if path_of_A/**relative_path_to_B** is existing dylib B is, this
> version of B is loaded
>
> 2- if path_of_A/**relative_path_to_B** is NOT can existing dylib B, then B
> is searched in the global system path.
>
> Is this correct?
>
> Anyhow, my first question is still valid:
>> install_name_tool allows changing the "id" of a dynamic library, with -id.
>> But What Does "id" Mean ?
>> And what is the impact of the lib's "id" on loading?
>> I've browsed the doc and the Net for long, but did not find any clear
>> info...
>
>
> Thanks,
> Nicolas
>
>
>
>> Hi folks,
>>
>> I am trying to make my applications distribution for mac OSX.4 and X.5,
>> but
>> have a couple of problem with the dynamic loading of libraries.
>>
>>
>> My first question is:
>> install_name_tool allows changing the "id" of a dynamic library, with -id.
>> But What Does "id" Mean ?
>> And what is the impact of the lib's "id" on loading?
>> I've browsed the doc and the Net for long, but did not find any clear
>> info...
>>
>>
>> My second question is:
>> What does @loader_path means exactly ?
>> I did not find any clear info on this, and basically, the observed
>> behavior does not match what the doc (apparently) says.
>>
>>
>>
>> Let's now get into a bit more details.
>>
>>
>> My distribution contains various executables, both bundled apps and
>> command-line, that rely on various interdependent libraries. The distrib
>> looks like:
>> distrib
>> |_ bin
>> |_ cmdlineexecutable
>> |_ application.app
>> |_ lib
>> |_ A.framework
>> |_ B.framework
>> where both executable depend on A AND B, and where A depends on B.
>>
>>
>> Since the executables are NOT on the same level in the distribution tree,
>> using @executable_path inside a library to refer to another library is NOT
>> possible.
>>
>>
>> I guess I have to use @loader_path: the executable would refer to a
>> libraries using @executable_path, and the libraries would refer to each
>> others using @loader_path
>>
>>
>> According to the doc:
>>> Library-relative location. To specify a file path relative to
>>> the location of the library itself,
>>> place the @loader_path macro at the beginning of the pathname.
>>
>> However, when using @loader_path, and when the framework is installed BOTH
>> inside my distribution AND in a system-searchable location (eg:
>> /Library/Framework) then BOTH versions of a library are loaded when
>> launching the app.
>>
>>
>> I guess that:
>> - the executable, that depends on frameworks A and B refered by using
>> @executable_path, loads the executable-relative versions of the frameworks
>> A and B
>> - framework A, that depends on framework B referred by using @loader_path,
>> loads the version of B which is located in /Library/Frameworks
>>
>>
>> Hence, @loader_path would NOT refer to the currently-loaded library
>> path... And the doc would lie :/
>>
>>
>> I would appreciate any help on this situation.
>>
>> Thanks much for your attention,
>> best-
>> Nicolas
>>
>> PS: First message on this list. I hope it I picked the correct list. Sorry
>> if I was wrong :/
>>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 24 Sep 2008 08:30:10 -0700
> From: "OSullivan, Steve" <email@hidden>
> Subject: PackageMaker exits with 0, but no installer package is
> created...help! :)
> To: <email@hidden>
> Message-ID: <C4FFAB13.12F5%email@hidden>
> Content-Type: text/plain; charset="US-ASCII"
>
> Howdy All,
>
> I am running this on Leopard 10.5.5, using Xcode 3.1.
>
> I am running this script in the hopes of building my installer, and placing
> the output in a specific folder.
>
> At this point, when I run the script, my target directory is created yet
> there is no package file output there.
>
> PackageMaker seems to exit with 0, and I see nothing indicating the problem
> in the verbose output.
>
> Can anyone offer some ideas on how I might proceed?
>
> Regards,
>
> Steve O'Sullivan
>
>
> # --- begin script
>
>
> #!/bin/sh
>
> # set -vx
>
> VERSION=$1
> BUILDVERSION=$2
> GETDATE=$(date +%m%d%y)
> CONSOLETARGET="/Volumes/TestingMac/target/Installers/target_${VERSION}_${GET
> DATE}/Console.pkg"
>
>
> packagemaker -r /pkg_base_console -o ${CONSOLETARGET} -i com.emc.company -n
> ${BUILDVERSION} -t company -l /Applications/company/ -g 10.5 -h system -b -v
>> pm_console_text.txt
>
> echo "packagemaker output: "$?
>
> if
> if [ $? == 0 ]
> then
> echo "pm_console.sh ran." >> /daily_build.txt
> exit 0
> else
> echo "pm_console.sh failed." >> /daily_build.txt
> exit 1
> fi
>
>
> # --- end script
>
>
>
> ------------------------------
>
> Message: 7
> Date: Wed, 24 Sep 2008 17:57:53 +0200
> From: Ulf Dunkel <email@hidden>
> Subject: Re: PackageMaker exits with 0, but no installer package is
> created...help! :)
> To: "OSullivan, Steve" <email@hidden>
> Cc: email@hidden
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Steve.
>
>> Can anyone offer some ideas on how I might proceed?
>
>> if
>> if [ $? == 0 ]
>> then
>> echo "pm_console.sh ran." >> /daily_build.txt
>> exit 0
>> else
>> echo "pm_console.sh failed." >> /daily_build.txt
>> exit 1
>> fi
>
> I wonder if the doubled 'if' is right here?
>
> HTH,
> UlfDunkel
>
>
> ------------------------------
>
> _______________________________________________
> Installer-dev mailing list
> email@hidden
> http://lists.apple.com/mailman/listinfo/installer-dev
>
>
> End of Installer-dev Digest, Vol 49, Issue 16
> *********************************************
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden