installation section of guide says to run configure when it shouldn't

[bugzilla.opendarwin.org@…]

​http://www.opendarwin.org/projects/darwinports/guide/ch01s03.html#install_dports says: === To install DarwinPorts execute the following commands from the darwinports/base directory.

% ./configure % make % sudo make install === it shouldn't be telling the user to run configure

[michaelm@…]

Users should run configure when building darwinports

[michaelm@…]

ok, debate on invalidness....

either the guide or the README is wrong....time will show which ;)

[bugzilla.opendarwin.org@…]

well the user guide is wrong in any case. if we want the user to run configure, we need to tell them to run: % ./base/configure right?

[bchesneau@…]

cd base and then ./configure is better since we should launch make in base directorye.

[bugzilla.opendarwin.org@…]

there is another instance of this problem at ​http://www.opendarwin.org/projects/darwinports/guide/ch01s04.html#updating_dports

[fkr@…]

we've decided: we want the user to run ./configure:

(from #opendarwin)

09:39 < wbb4> so do we prefer 'cd base; ./configure && make && make install' or 'make && make install' from darwinports/ ? 09:40 < fkr> heh, I'd say latter, since then our users get used to having run a ./configure script 09:40 < fkr> that will likely offer more features in the future 09:40 < wbb4> the former, you mean? 09:40 < fkr> yes :) 09:40 < wbb4> ok :) 09:40 < fkr> but the Mac-Guys will probably scream and shout over that. 09:40 < fkr> but that's why we will have an installer 09:40 < wbb4> heh 09:41 < fkr> landon? 09:43 < landonf> yep? 09:44 < fkr> what's your opinion on that? 09:44 < landonf> Oh 09:44 < landonf> People should run configure 09:45 < landonf> We provide the make-foo just to be nice to people that have always done it the other way

[wbb4@…]

I think 'cd base/; ./configure && make && make install' (to paraphrase) is the best way.

I agree that we need to change the README instead of the Guide.

The reason for this is that we may want to give users additional configure options in the future (not that we don't already), and it's better to keep the documentation consistent, instead of saying:

"All you have to do is cd darwinports/ and type 'make'. Unless of course, you want to do FOO, then you need to cd darwinports/base and type ./configure --with-foo and then make..."

It's a bit clearer to say:

"To build DarwinPorts, cd darwinports/base and type ./configure. If you want to use FOO, add '-- with-foo' to the command. Then type make, and then sudo make install."

(Although even that could be stated better, sorry, it's early in the morning and I've yet to have my tea.)

Thoughts?

[toby@…]

This was taken care of long ago. Closed.