From owner-freebsd-ports@FreeBSD.ORG Mon Sep 16 09:51:29 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D61042DC for ; Mon, 16 Sep 2013 09:51:29 +0000 (UTC) (envelope-from spankthespam@gmail.com) Received: from mail-qe0-x22b.google.com (mail-qe0-x22b.google.com [IPv6:2607:f8b0:400d:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 990412B9C for ; Mon, 16 Sep 2013 09:51:29 +0000 (UTC) Received: by mail-qe0-f43.google.com with SMTP id gh4so2663897qeb.30 for ; Mon, 16 Sep 2013 02:51:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Qo3od9ZrXGXbHrTJruZsrywRLlCvdRRSqEj/UUSQ5Gc=; b=0RqU1w8d1GyKdn9dgZ5t3yo51IKiZTVi2wPzB/be3mJDLUjoAh1oHgaSh9HIyya+re xPo/1nH+MzufK3Vd3adphY3KIQ8EZR4xMqhqEm9ghf6oguYcxxT4U3r/WiXvxMwsFI5X lA7qtadHrdQUoWHOhlXcmfD4juEnyJ2V9HAXGX8aNT+jNjU6ZL3FSlUtExEfiPdbI+WN Ow1Ufw1Haf4MJ52SKpIiXHLdWdc9dTTDuV0EnFW/TJ0aj+Uxb4HdlGIRRAvBDmhJI3bl RbRfTJVqmMoVfkBKWRjIjNuBOYGuLopvrXfb16Wb+toaHOlnmaL88V4yBYuphyeNXZyB m6rw== MIME-Version: 1.0 X-Received: by 10.224.69.133 with SMTP id z5mr13640270qai.50.1379325088819; Mon, 16 Sep 2013 02:51:28 -0700 (PDT) Received: by 10.229.205.71 with HTTP; Mon, 16 Sep 2013 02:51:28 -0700 (PDT) In-Reply-To: References: Date: Mon, 16 Sep 2013 10:51:28 +0100 Message-ID: Subject: Re: How to correctly generate pkg-plist From: SpamMePlease PleasePlease To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Sep 2013 09:51:30 -0000 Hi, I was wondering if there's anyone who could give me some advice on it? This is an issue that stops me from sending otherwise fully working port. Regards, S. On Sat, Sep 14, 2013 at 2:18 PM, SpamMePlease PleasePlease < spankthespam@gmail.com> wrote: > Hi, > > I am writing new port that compiles and installs huge number of Erlang > libraries. Everythig is working fine until there's a need of deinstallation > or to make package - the problem is that the user might have older Erlang > version (for example, coming from ports unpacked during installation from a > cd) and when compiled with such Erlang, everything will be working, except > for the fact that older Erland will compile different versions of > libraries, and therefore my 2000 lines long pkg-plist will no longer be > valid. I thought I can remedy that simply by not listing the lib names and > their dir paths to avoid such situation, but to use @unexec ${RM} -rf > lib/portname, but then there's a problem with make package, that is not > containing all required and compiled libs. > > How to solve that situation? > > Regards, > S. >