Date: Sat, 29 Jan 2005 20:25:33 +0100 From: Gert Cuykens <gert.cuykens@gmail.com> To: Phil Schulz <ph.schulz@gmx.de> Cc: freebsd-questions@freebsd.org Subject: Re: message for port developers Message-ID: <ef60af09050129112555a8c8cb@mail.gmail.com> In-Reply-To: <ef60af09050129112137c41279@mail.gmail.com> References: <ef60af090501290942568a3cbe@mail.gmail.com> <41FBCF95.3020706@gmx.de> <ef60af0905012910171bb98a81@mail.gmail.com> <ef60af090501291022196ccd70@mail.gmail.com> <ef60af09050129102721cbbafb@mail.gmail.com> <41FBD8ED.1070503@gmx.de> <ef60af09050129112137c41279@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 29 Jan 2005 20:21:08 +0100, Gert Cuykens <gert.cuykens@gmail.com> wrote:
> On Sat, 29 Jan 2005 19:41:49 +0100, Phil Schulz <ph.schulz@gmx.de> wrote:
> > On 01/29/05 19:27, Gert Cuykens wrote:
> > > On Sat, 29 Jan 2005 19:22:18 +0100, Gert Cuykens <gert.cuykens@gmail.com> wrote:
> > >
> > >>On Sat, 29 Jan 2005 19:17:46 +0100, Gert Cuykens <gert.cuykens@gmail.com> wrote:
> > >>
> > >>>On Sat, 29 Jan 2005 19:01:57 +0100, Phil Schulz <ph.schulz@gmx.de> wrote:
> > >>>
> > >>>>I'm not a port developer but I think you are looking for either `make
> > >>>>configure` or the BATCH variable.
> > >>>>
> > >>>> If you know which ports you want to install on your system, you can do
> > >>>>a `make configure' for each port (where it is availeable) and then have
> > >>>>a skript fire up the `make install's. I'm not sure though if that works
> > >>>>recursively, i.e. you run `make configure' for e.g. the Gnome meta port
> > >>>>and you configure all the dependencies with that one command. Why don't
> > >>>>you try it? ;-)
> > >>>> If you think the default options are ok for you, you can add a line
> > >>>>like "BATCH=yes" in /etc/make.conf and the ports will be built w/o any
> > >>>>user interaction. Very useful for large builds.
> > >>>>
> > >>>>HTH,
> > >>>>
> > >>>>Phil.
> > >>>>
> > >>>
> > >>>BATCH=yes i can not do because some configuration leave some very nice toys out.
> > >>>
> >
> > If you know what specific options you are looking for, you could
> > configure the ports "by hand" and install them later. I think not all
> > ports can be build with BATCH defined, at least that's what ports(7)
> > suggests.
> >
> > >>>Now lets see you can call all dependencies with this if your index is working :)
> > >>>
> > >>>make pretty-print-build-depends-list
> > >>>so with some grep magic you could tell to do make config in all does
> > >>>dependencies. Now the trickie part how do you find out the new
> > >>>dependencies after does configure screens ?
> > >>>
> > >>
> > >>a maybe updating the index and do the same thing all over again until
> > >>there are no new dependencies ?
> > >>
> > >
> > >
> > > can you update the index after a configure that adds a extra
> > > dependencie to the port ?
> > >
> >
> > I don't know.
> >
> > I don't think it would be very efficient in terms of effort vs. use. How
> > many ports do you really want to install with non-default options? And
> > how often do you re-configure them?
> >
> > You probably want to wait for an opinion from someone else who knows
> > more, though.
> >
> > Phil.
> >
>
> Lest see how far we can get you have to help me do because i suck at
> development :)
>
damn forgot to rename currentdependencies to dependencies
> main{
> newdependencies= yes;
> dependencies = make pretty-print-run-depends-list;
>
> WHILE newdependencies=yes DO
> configure(dependencies);
> dependencies=(make pretty-print-run-depends-list) - (dependencies)
> IF dependencies = nulll {
> newdependencies = no
> }
> }
>
> function configure(dependencies){
> WHILE dependencies DO{
> grep(dependencies,i);
> make configure;}
> }
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ef60af09050129112555a8c8cb>