Package System specification, revisited
- To: lsb-spec@lists.linuxbase.org
- Subject: Package System specification, revisited
- From: Raul Miller <moth@magenta.com>
- Date: Wed, 3 May 2000 11:47:44 -0400
- Message-id: <[🔎] 957368641.45cb11e0@magenta.com>
- In-reply-to: <38F91D4E.9AEAF0F@transmeta.com>; from hpa@transmeta.com on Sat, Apr 15, 2000 at 06:54:22PM -0700
- References: <Pine.LNX.4.10.10004141302560.23724-100000@www.slackware.com> <38F78292.D5A3FE3E@transmeta.com> <08d401bfa717$54dcb4e0$1f215dcf@rpp586> <38F8CCA5.C815CCE6@transmeta.com> <08ee01bfa732$e7249140$1f215dcf@rpp586> <38F90787.1EC9043E@transmeta.com> <093e01bfa746$0a0aea20$1f215dcf@rpp586> <38F91D4E.9AEAF0F@transmeta.com>
[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
Reply to: