Re: 21.0 showstopper bytecompile-time -vs- run-time dependencies

Friday, 16 October 1998

        Olivier Galibert <galibert(a)pobox.com&gt; writes in xemacs-beta(a)xemacs.org:

...
 On Thu, Oct 15, 1998 at 11:15:50PM -0700, SL Baur wrote:
> Before I forget ...
> 
> The current REQUIRES field is only a bytecompile-time dependency not a
> run-time dependency and should *never* be enforced at run-time,
> including package fetching.
> 
> Since not all run-time dependencies should be enforced either
> (eg. Gnus run-time dependency on rmail), the solution isn't a
> straightforward download everything.
> 
> Suggestions? 
...
 Three fields:
 - minimal requires for runtime
 - requires for compile time
 - full requires for maximal operation 
Exactly correct.  The minimal requires would be force-downloaded by
the package-get stuffs.  The maximal requires would need some kind of
extra option.

For a first cut, I'd be satisfied to have minimal requires handled
correctly as the SUMO tarballs will handle everything else.

...
 But maybe that would be too much a hassle to manage... 
At the present time, yes.  We *really* need some tool to compute
run-time dependencies.

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998