.include "files/somefile" before .include <bsd.port.pre.mk>

Ion-Mihai Tetcu itetcu at people.tecnik93.com
Thu Aug 26 17:18:56 PDT 2004

On Fri, 27 Aug 2004 01:08:11 +0200
Oliver Eikemeier <eikemeier at fillmore-labs.com> wrote:

> Ion-Mihai Tetcu wrote:
> > Thanks for help.
> >
> > Well, a few day ago when I stepped into the office, one one of my
> > colleagues desktop (he is running enlightenment wm) I've seen a nice
> > LCARS Star Trek interface. After spending nearly 12 hours searching the
> > net for something similar for KDE, but with no luck, I've email kde@ and
> > lauri at kde.org passed my some links, including an incomplete such a theme
> > that includes a LCARS skin for xmms, suggesting I try to bring up to
> > date the theme (it's for kde2).
> >
> > Digging around in the ports tree I didn't found any xmms skin port, so I
> > thought I could do a more complete job that just the LCARS skin.
> >
> > Attached are the Make file and distinfo for the master port, which
> > server also as a meta-port and a Makefile for a slave (skin category,
> > type) port.
> http://www.1001winampskins.com/copyright.html says:
> "you may not link to images and downloadable files found on this website 
> within referring web documents"
> I'm not sure whether this means manual download.

So I put the url of each the page in the pkg-descr; or my English plays
my some tricks ?

> OTOH it says: "All 
> skins found on this site are copyrighted by their respective authors. 
> Detailed copyright information to each individual skin may be included 
> in the corresponding downloadable skin-files."

I've read about 50 of them and it doesn't seems to be any problem. And
I've planned to review each .wsz by hand anyway.

> So IMHO it would be best to download the skins, unpack them, examine the 
> copyright and repack them all together in one tgz.
> > I've wrote a script to parse the WWW site and auto-create each slave
> > port and I want to use a variant of it for updating and having the
> > distfiles in another file would make the job much easy.
> Uhm, I'm not sure whether this will work. Are you sure you won't violate 
> any copyrights by this?

By fetching, parsing and generating some text files ? No, Google does it
each second  :)

Marking them NO_CDROM, NO_PACKAGE should be safe enough, I think.

> > The SKIN_PORTS I want to included from a file (it's commented out in the
> > Mkefile, not complete, it should be PORTNAME.PORTVERSION so that the
> > meta-port can RUN_DEPEND on some file to know when a port have changed)
> Anyway, wouldn't it be better to have just one (or a couple of) 
> collection(s) instead of a huge number of slave ports?

On the second thought you are right, since the name -> option doesn't
usually provide any hint about the skin. And have options just for the

But I've started with a big Makefile and I come to just love make's
variables substitution ;)

> > BTW, for DISTFILES like ``ReaperPro(BluE).wsz'',
> > ``[rustedoldthing].wsz'' I can't make it work, esp. in variables
> > substitution (see the makefile).
> This is doable, but probably not worth the effort.

Yeh ?  didn't managed.

> Repackaging seems like a viable solution here.

Just that I'm not sure I want to host 100MB of skins for download ;) I
have no problems with portindex or dspam, but they are much smaller and
more useful.


Unregistered ;) FreeBSD "user"

More information about the freebsd-ports mailing list