From owner-freebsd-ports@FreeBSD.ORG Tue Aug 5 10:57:32 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C571D1065677 for ; Tue, 5 Aug 2008 10:57:32 +0000 (UTC) (envelope-from ady@ady.ro) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174]) by mx1.freebsd.org (Postfix) with ESMTP id A3EA38FC1F for ; Tue, 5 Aug 2008 10:57:32 +0000 (UTC) (envelope-from ady@ady.ro) Received: by wf-out-1314.google.com with SMTP id 24so2157239wfg.7 for ; Tue, 05 Aug 2008 03:57:32 -0700 (PDT) Received: by 10.142.253.21 with SMTP id a21mr5373506wfi.254.1217933852134; Tue, 05 Aug 2008 03:57:32 -0700 (PDT) Received: by 10.142.54.14 with HTTP; Tue, 5 Aug 2008 03:57:32 -0700 (PDT) Message-ID: <78cb3d3f0808050357g7f0ab5a7v615bd17cecde5e3c@mail.gmail.com> Date: Tue, 5 Aug 2008 12:57:32 +0200 From: "Adrian Penisoara" Sender: ady@ady.ro To: "Christopher Hall" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5151c41d0808031258m5c0c35eeu63c24935afa05b1f@mail.gmail.com> X-Google-Sender-Auth: ca2f62c96285baba Cc: Alex Kloss , freebsd-ports@freebsd.org Subject: Re: Help needed porting Quod Libet plugins X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Aug 2008 10:57:32 -0000 Hi, On Mon, Aug 4, 2008 at 3:45 AM, Christopher Hall wrote: >> The plugins are single-file Python scripts, which you simply drop into >> /usr/local/share/quodlibet/plugins/ and then enable in Quod Libet. In >> order to download them, you must pull them from Quod Libet's trunk in >> Subversion. This doesn't sound like a good idea to me, because there's >> no way to guarantee that a given plugin will remain stable all the >> time. If I ported a plugin, is it advisable to pull the distfile from >> trunk? > > What about pulling a particular Subversion revision that is the way I did it > I had a do-fetch target that fetched the subversion revision to a > subdirectory > in /usr/ports/distfiles then used tar to make a file-rev.tar.bz2. Then just > carry on as normal. I do not want to clutter the list with this Makefile > I could send to directly if you think it might help. > What about overriding the fetch and extract targets altogether with the above steps (e.g. the "fetch" target to do a "svn co" and the "extract" target just to place the proper files under $WRKSRC) ? Regards, Adrian.