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

[Ion-Mihai Tetcu]

On Fri, 27 Aug 2004 00:16:34 +0200
Oliver Eikemeier <eikemeier at fillmore-labs.com> wrote:

> Ion-Mihai Tetcu wrote:
> 
> > On Thu, 26 Aug 2004 23:56:44 +0300
> > Ion-Mihai Tetcu <itetcu at people.tecnik93.com> wrote:
> >
> >> On Thu, 26 Aug 2004 22:41:36 +0200
> >> Mathieu Arnold <mat at FreeBSD.org> wrote:
> >>
> >>> +-Le 26/08/2004 23:32 +0300, Ion-Mihai Tetcu a dit :
> >>> | Hi,
> >>> |
> >>> |
> >>> | Is it legal to include a file from files _before_ including
> >>> | bsd.port.pre.mk ?
> >>> |
> >>> | I need to obtain some long lists ( of DISTFILES and slave ports) and
> >>> | having them in a separate file would make maintenance much more 
> >>> easy.
> >>> |
> >>> | The problem I see is that .CURDIR is not defined; does this break
> >>> | something ?
> >>>
> >>> .CURDIR is an internal make variable, it's not defined by bsd.*.mk :
> >>>
> >>>
> >>> mat $ cat Makefile
> >>> test:
> >>>         @echo ${.CURDIR}
> >>> mat $ make test
> >>> /home/mat
> >>
> >> slave-ports-list contains:
> >> SLAVE_PORTS= slave_port 1 \
> >> slave_port2 \
> >> .... etc ........
> >>
> >> ..............
> >> .include "${.CURDIR}/files/slave-ports-list"
> >> .for port in ${SLAVE_PORTS:O}
> >> OPTIONS+= ${port} .......
> >> .endfor
> >> .include <bsd.port.pre.mk>
> >> ............
> >>
> >> on make it search slave-port-list  in /
> >> Same (and expected) if I put ${FILESDIR}/slave-ports-list"
> >
> > Uh, sorry, it's working with ${.CURDIR}/files (and, of course not with
> > FILESDIR), but portlint -CN complain:
> > WARN: Makefile: possible direct use of "files" found. if so, use 
> > ${FILESDIR} instead.
> >
> > And I want do do the same for the DISTFILES.
> >
> > So I'm asking if it's OK to do so (e.g. portlint point of view) as I
> > don't want write it all again if it doesn't obey style.
> >
> >>> What problem are you trying to solve ?
> >>
> >> Trying to have some infrastructure to easily maintain a port with about
> >> 1000 distfiles by breaking it in slave ports and having a metaport to
> >> install the small ones.
> >
> > And I have some scripts hat automate the a large part of the process.
> 
> Could you be more concrete? I fear that a port having 1000 distfiles is 
> not too friendly to users machines, so maybe we could find another 
> solution, like repackaging it. To make a concrete suggestion I have to 
> learn more about your problem, so could you tell us which software you 
> are porting and maybe give us a pointer to the Makefiles so far?

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.

They seems to work OK (e.g. istanll, deinstall, etc.), except a few
portlint complains.

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.

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)

BTW, for DISTFILES like ``ReaperPro(BluE).wsz'',
``[rustedoldthing].wsz'' I can't make it work, esp. in variables
substitution (see the makefile).


Thanks,

-- 
IOnut
Unregistered ;) FreeBSD "user"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Makefile
Type: application/octet-stream
Size: 2703 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040827/3a9af85b/Makefile.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: distinfo
Type: application/octet-stream
Size: 14774 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040827/3a9af85b/distinfo.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Makefile
Type: application/octet-stream
Size: 2406 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040827/3a9af85b/Makefile-0001.obj