Re: nextstep packaging system

[Rogelio Serrano]

it seems that the pkg directory is copied to Library/Receipts, the
payload unarchived and deleted.

How simple is that!

On Fri, Feb 28, 2014 at 10:01 AM, Rogelio Serrano
<rogelio.serrano@gmail.com> wrote:
> Thanks!
>
> Finding out why it didnt work well makes it interesting and helps
> design a better one.
>
>
>
> On Fri, Feb 28, 2014 at 9:52 AM, Graham Lee <graham@iamleeg.com> wrote:
>> Substantially the same way that the Mac OS X .pkg system works, although
>> that’s been refined over time.
>>
>> So there’s a bundle called a pkg, which contains two useful elements: a
>> zipped PAX archive containing the payload and a “bill of materials” which
>> describes the locations, permissions and sizes of the payload files and
>> folders. Installing involves dropping the payload into place and the BOM
>> into a known location: I can’t remember where that is now and will probably
>> never need to know again :). There’s no reference counting or versioning of
>> installed files, which makes uninstallation, upgrades and downgrades
>> difficult and makes it a bad model to base another package system on.
>>
>> More here: http://www.bangmoney.org/nextstep/packages_1.html
>>
>> Graham.
>>
>> On 28 Feb 2014, at 09:45, Rogelio Serrano <rogelio.serrano@gmail.com> wrote:
>>
>> hi
>>
>> How did the nextstep package system work?
>>
>> _______________________________________________
>> Discuss-gnustep mailing list
>> Discuss-gnustep@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnustep
>>
>>