Re: [OctDev] Re: make clean

[Paul K. <pki...@us...>]

Yeah, I was thinking about what would be required this morning
and deciding that it wasn't going to be so easy as I thought.  Any
idea how Octave does it?  After all, Makefile doesn't exist before
configure is run.  Having a 'dist.sh' script in each subdirectory
that needs it is another way independent of make of doing this,
though since we always have 'Makefile' around in octave-forge
this isn't so compelling.

Thanks,

- Paul

On Jul 7, 2004, at 5:45 AM, David Bateman wrote:

> Ok, I've committed a change that builds the fixed and comm packages
> docs as part of the "make dist" target and removed the texinfo and
> postscript files from the repository.
>
> I had to allow the dist, distclean and clean targets to propogate to
> the subdirectories even without the Makeconf file being available.
> For this reason I had to change "include Makeconf" to "sinclude
> Makeconf" basically everywhere.
>
> If the Makeconf file exists when you do the "make dist" this is the
> surest way to get things right. Otherwise the variables MKTEXI, DVIPS,
> etc are set to default values in main/{comm,fixed}/doc/Makefile
> that should probably work, but no guarentees.
>
> Regards
> David
>
> Dapr=E8s Paul Kienzle <pki...@us...> (le =
07/07/2004):
>>
>> On Jul 6, 2004, at 8:29 AM, David Bateman wrote:
>>
>>> According to Paul Kienzle <pki...@us...> (on
>>> 07/06/04):
>>>>
>>>> My preference is to put the docs somewhere on the website for
>>>> those who can't build them, and use something like 'if not built
>>>> then echo "Docs not built.  Get them from octave.sf.net"'.
>>>
>>> Errr, that's harder due to the fact that I'd have to test for the
>>> presence of perl and a properly installed texinfo package. The way
>>> I proposed in what the octave distributions do themselves, and so
>>> I'd be happy with this way. Also I install the texinfo file, so that
>>> online help is available from within octave itself. If the file is
>>> not built or not part of the distribution, then this online help
>>> won't be available.....
>>>
>>> In any case I checked in the change that includes the postscript and
>>> texinfo help files as part of the distribution. If you really think=20=

>>> its
>>> a bad idea given the above, I'll have to rethink what to do...
>>
>> Okay, how about we have a 'make dist' target that builds these
>> and cleans up any intermediate files.  That way people installing
>> the release tarball have what they need and only the release
>> manager needs to have all the required tools installed.   You are
>> welcome to release as often as you need.
>>
>> Paul Kienzle
>> pki...@us...
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email sponsored by Black Hat Briefings & Training.
>> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
>> digital self defense, top technical experts, no vendor pitches,
>> unmatched networking opportunities. Visit www.blackhat.com
>> _______________________________________________
>> Octave-dev mailing list
>> Oct...@li...
>> https://lists.sourceforge.net/lists/listinfo/octave-dev
>
> --=20
> David Bateman                                =
Dav...@mo...
> Motorola CRM                                 +33 1 69 35 48 04 (Ph)
> Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax)
> 91193 Gif-Sur-Yvette FRANCE
>
> The information contained in this communication has been classified =
as:
>
> [x] General Business Information
> [ ] Motorola Internal Use Only
> [ ] Motorola Confidential Proprietary
>