This is the mail archive of the automake-prs@sources.redhat.com mailing list for the automake project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

automake/313: try not to clean distributed files



>Number:         313
>Category:       automake
>Synopsis:       try not to clean distributed files
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    tromey
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Apr 12 10:51:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Alexandre Duret-Lutz
>Release:        1.6.1
>Organization:
>Environment:

>Description:
There are some files Automake always cleans for you, 
without wondering whether they are distributed or not. 

It would be nice if distributed files was not included
in {MOSTLY,}CLEAN.

For instance on

  info_TEXINFOS = doodad.texi
  EXTRA_DIST = doodad.ps

Automake could decide to clean `doodad.ps' on 
`maintainer-clean' instead of `mostlyclean'.


>How-To-Repeat:

>Fix:
An idea:
1. Have a central place where all primaries and 
   magic variables (e.g. EXTRA_DIST) are defined.
   The definition would say whether the content
   is distribued or not, whether the primary support
   the nobase_ feature, which directories it can be installed
   in, etc.  (Using this instead of the arguments to
   &am_primary_prefixes would make the code cleaner in my 
   opinion). 
2. Use the above "database" to browse all defined 
   variables and build a map of distributed files.
3. Lookup this map before deciding to clean a file.
   Using this map, warn about files which are 
   cleanable AND distribuable.
>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]