Hi,
I have a fourth option. Use the Depends: mechanism to make
dpkg do the right thing on individual add-on installs (like, if your
package strictly depends on another). However, internally,
emacsen-common goes the extra mile.
Secondly,
> So, each emacs add-on package should provide a file like
> /usr/lib/emacsen-common/dependencies/<pkg-name>, which contain lines
> like
>
> <pkg-name> dependnecy-one
> <pkg-name> dependnecy-two
>
> emacsen-common merely concatenates all these files together
> and runs them through tsort, and bingo: depndency order compilations
> are possible.
The emacs-install script could then do something like menu
does, wait in the background for dpkg to finish, so that all
add-ons to be installed in this run are done, and then look at the
files above to figure out the emacsen-compile order.
The files added by each package can be a superset of the
dependencies specified, so they may also take into account ``soft''
dependencies.
manoj
--
Seeing the foam-like nature of the body, and awakening to its
mirage-like quality, one can escape the sight of the King of Death,
snapping Mara's flowery bonds. 46
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
