From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-oi0-f48.google.com ([209.85.218.48]) by pp; Mon May 11 17:45:04 EDT 2015
Received: by oign205 with SMTP id n205so115595840oig.2
        for <9front@9front.org>; Mon, 11 May 2015 14:45:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=kNJ6Ck1ucQIgrfcIdAGPeuqvOSAsLkpcAjsZezshKKs=;
        b=v710zIo+w2/SKJ/FehyC4+ooDc2dWKbrJRrPsA0MmbMdQ3yCFTNZZArkBcjXBSWEXp
         1jnx0gbTKU+rvhxSmHbIPuXi85fVSOn5ysCqdmUy0ERfO0YqPltJ8PqvxNVezXRLhSid
         PdBNPqKa6QEwa6ESZJuqL8yhEvpjWsDtl5NIJfqTZCC58ji1rYMXVzZzd5aG0UBeAlHM
         OsaGiiGejNGXvOm7w4jwgc8bJrnIEP5txIf2jRu4XAYMp8Q29Lqve7GtnqVb562Ks6XI
         k2zMAQ52qBFYBQ9AVykLMZTycH8sdDFFuQcW6MQ6pr+LmKFROBxX8APF5cVPAoqRASky
         wUjQ==
X-Received: by 10.202.49.11 with SMTP id x11mr9105265oix.63.1431380703144;
 Mon, 11 May 2015 14:45:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.88.85 with HTTP; Mon, 11 May 2015 14:44:42 -0700 (PDT)
In-Reply-To: <eddfdf06d141880bf717d6fc4066e519@u2.sfldmibb.det.wayport.net>
References: <eddfdf06d141880bf717d6fc4066e519@u2.sfldmibb.det.wayport.net>
From: =?UTF-8?Q?Iruat=C3=A3_Souza?= <iru.muzgo@gmail.com>
Date: Mon, 11 May 2015 18:44:42 -0300
Message-ID: <CABJnqBRHBaTFDY8qVytcSQWz7yJg--BtUQ_qXrp_CV6VrtCs6g@mail.gmail.com>
List-ID: <9front.9front.org>
X-Glyph: ➈
X-Bullshit: RESTful open high-performance content-driven element layer
Subject: Re: [9front] pkg/unpkg strangeness
To: 9front@9front.org
Content-Type: text/plain; charset=UTF-8

Unpkg tries to be a tar xv printing "A path" to stdout and "path
checksum" to stderr.
It only knows about the tar format (100 chars limit in path), but
tar(1) compresses using ustar (256 chars limit in path) if needed.

imo, unpkg should be rewritten in rc.

On Mon, May 11, 2015 at 6:33 PM,  <sl@9front.org> wrote:
>> According to tar(1):
>>
>> File path names are limited to 100 characters (256 when
>>           using ustar format).
>>
>> Every file that has a path bigger than that leads to pkg/unpkg trying
>> to unpack the file into /.
>
> I don't see where tar(1) is ever getting called.
>
> Note: I do not really understand unpkg.c.
>
> sl