Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Linux standards

On Thu, 20 Jun 2002, John Chambers wrote:

> Jerry Feldman writes:
> | Most of the better apps require the following steps:
> | 1. ./configure [ configure arguments ]
> | 2. make
> | 3. become root.
> | 4. make install
> | 5. become non-root.
> Hey, you forgot a very common (and important) step:
>   2.5. make test

And the just-as-common (at least for big packages):
    2.1. make coffee

There's a problem with a universal packaging system that works across 
distros, and it was touched on at the meeting last night: file locations 
and formats.  Different distros put very critical things in different 
places.  A universal package manager would have to deal with that.

Not that it couldn't be done.  A cool way to handle that would be a 
package format that permitted macros for directories and files and other 
resources, and let the package manager (user-configurably) handle the 
macro expansion.

For instance, a package could ask the package manager to install 
"%localbindir%/mybinary" and the package manager would know the right 
directory to put it in.  You would need %man3dir%, %usercronfile%, 
%locallibdir%, %perlmoduledir%, %startupnetfile%, and probably at least a 
dozen more.

You would need something AT LEAST that powerful and flexible.

DDDD   David Kramer         david at
DKK D  "Questions are a burden to others,
DK KD  Answers a prison for oneself."
DDDD                                                           -The Prisoner

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /