Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Aug 2008 12:57:32 +0200
From:      "Adrian Penisoara" <ady@freebsd.ady.ro>
To:        "Christopher Hall" <christopherhall.hsw@gmail.com>
Cc:        Alex Kloss <klossalex@gmail.com>, freebsd-ports@freebsd.org
Subject:   Re: Help needed porting Quod Libet plugins
Message-ID:  <78cb3d3f0808050357g7f0ab5a7v615bd17cecde5e3c@mail.gmail.com>
In-Reply-To: <ED31C50E-6E91-4CE7-B944-06C941DF3C4F@gmail.com>
References:  <5151c41d0808031258m5c0c35eeu63c24935afa05b1f@mail.gmail.com> <ED31C50E-6E91-4CE7-B944-06C941DF3C4F@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

On Mon, Aug 4, 2008 at 3:45 AM, Christopher Hall
<christopherhall.hsw@gmail.com> 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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?78cb3d3f0808050357g7f0ab5a7v615bd17cecde5e3c>