| To: | Michel Schinz <Michel.Schinz@epfl.ch> |
|---|---|
| Subject: | Re: [Scsh-hackers] scsh-packages first contact |
| From: | Anthony Carrico <acarrico@memebeam.org> |
| Date: | Fri Feb 20 06:22:07 2004 |
| Cc: | scsh-hackers <scsh-hackers@lists.sourceforge.net> |
| List-id: | Discussion among the implementors <scsh-hackers.lists.sourceforge.net> |
| Sender: | scsh-hackers-admin@lists.sourceforge.net |
Yes. Now we are on the same page. If you don't have a top level package, "load-package-in" has an advantage of over "install-sub-package": install-sub-package forces you to have a top level package even if it is just an empty directory (and probably a symbolic "active" link to that directory unless you are careful to save and restore the option). The only other reason I can think of to choose one over the other might be an ordering issue, for example if the top level package depends on its child to be compiled for bootstrapping or something like that. I'll play with both choices for a bit. -- Anthony Carrico |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Scsh-hackers] scsh-packages first contact, Michel Schinz |
|---|---|
| Next by Date: | [Scsh-hackers] Install-lib: user-specific default options, Michel Schinz |
| Previous by Thread: | Re: [Scsh-hackers] scsh-packages first contact, Michel Schinz |
| Next by Thread: | Re: [Scsh-hackers] scsh-packages first contact, Anthony Carrico |
| Indexes: | [Date] [Thread] [Top] [All Lists] |