Re: Package System specification, revisited

["Philip Rackus" <philipr@corel.com>]

Hi Raul,

An application typically can be contained in a package or a set of packages. In
either case it doesn't matter because you (the developer) determine the package
dependencies.

The package(s) that make your application may have dependencies (it may not).
If you depend on a package that is not part of an LSB distribution and you don't
include that package with your application (thus making it part of your
application) then it won't be LSB compliant, because it won't run on a stock LSB
system.

Phil

(and yes assigned name space is important)



Raul Miller wrote:

> [Sorry to bring up old material, but...]
>
> On Sat, Apr 15, 2000 at 06:54:22PM -0700, H. Peter Anvin wrote:
> > Your application can create its own dependencies (an application may
> > obviously want to contain more than one package), but think about
> > it for a second -- if you have dependencies outside of LSB and your
> > own application, it obviously can't be LSB compliant, since you're
> > depending on something that isn't in LSB!
>
> I want to make sure I understand this: is an application a package,
> or can an application be a set of packages?
>
> Which is to say: if an application is a set of packages, some of which
> depend on other packages from within the application, is that application
> LSB compliant?
>
> [Aside: if there's no global name space out of which package names are
> allocated then there will be completely different packages which have the
> same name.  That might be significant if there's ever to be an LSB 2.0,
> and might also be significant for people writing documentation, etc.]
>
> Thanks,
>
> --
> Raul
>
> --
>
> To UNSUBSCRIBE, email to lsb-spec-request@lists.linuxbase.org
> with subject of "unsubscribe". Trouble? Email listmaster@lists.linuxbase.org