Re: package-get.el : package-get-user-package-location

Monday, 23 August 1999

        sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:

...
 >> This looks wrong.  Packages go into a package hierarchy, and
~/.xemacs
 >> isn't one. 
It is/was in 21.1. 

...
 >> The general concept of having a single package hierarchy
 >> into which user packages go is broken by now. 
Huh? Why?

...
 >> Actually, looking at
 >> package-get.el (for the first time), the entire logic associated with
 >> `package-get-user-package-location' is complete bogus. 
Apart from the obvious bug with the missing ~, could you please define 
bogus?

...
 Well, if you want to really fix the problem, you need to coordinate
 the workings of `package-get-user-package-location',
 `package-get-maybe-save-index', and `package-get-locate-index-file'. 
They are coordinated. If you fix the stupid ~ problem and it works.

...
 Especially the latter is totally sloppy and should be rewritten.

Please define 'sloppy'. 

...
 There's clearly a blatant bug here, but I'd rather leave this
eyesore
 in to remind people things are really broken here, rather than going
 for the quick fix. 
Please define broken? It al does what it is supposed to (modulo "~")

1. Get the package index from the best location possible.
2. Get the file locally using the standard XEmacs data file
   algorithms.
3. If the two don't match offer to update the local file if we can
   write to it.
4. If we cannot write to it, offer to write it to a location where the 
   user is likely to be able to write and where XEmacs will find it
   again (i.e. the etc directory of the users package hierarchy).

Jan

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