On 8/29/11, Игорь Пашев <pashev.i...@gmail.com> wrote: > 2011/8/29 Joseph R. Justice <jayare...@gmail.com> > >> "interpsys" would be a Build-Depends of some sort for OpenAxiom then, > > No, interpsys is a part of OA sources and used only for building. > As I said before, one can think of it as of libtool or similar.
OK. I wondered, because in ... mail from David Bremner <brem...@debian.org> dated Sun, 28 Aug 2011 12:00:38 -0300, message-id <87k49xy415.fsf@zancas.localnet>, he claimed interpsys "isn't included in the open-axiom source package" (assuming I read his message correctly). That's why I wondered where interpsys was coming from. Perhaps Mr. Bremner was mistaken, however. (Talking about my concerns about "SBCL core" being included within OpenAxiom, without OpenAxiom run-depending on SBCL): >> Might this cause a problem for someone down the line? I'm thinking of >> something along the lines of, a bug (possibly a security-related bug) >> is found in SBCL (possibly by SBCL upstream), in the portion that is >> duplicated inside of OpenAxiom, and is fixed in the SBCL package >> itself within Debian. > > AFAIK this is how most lisp compilers work: include its core into resulting > binaries. OK, I think I understand. I saw (IIRC) that OpenAxiom Build-Depends on SBCL. Without having previously done Debian packaging... I presume that means that if SBCL has a security-fix of a sort that would affect the portion of SBCL that is incorporated into stand-alone binaries created using SBCL (e.g. OpenAxiom), that when SBCL is patched and rebuilt, this will automagically force the rebuilding of all packages that Build-Depends on SBCL (e.g. OpenAxiom) without further human intervention, so that those packages will eventually incorporate the fix made to SBCL? Or, is this incorrect, and if so what needs to be done and/or who needs to be aware of this connection between OpenAxiom and SBCL such that if if there *is* a fix to SBCL that needs to be incorporated into OpenAxiom also, it will be duly incorporated into OpenAxiom either automatically and/or through manual actions being taken by whomever needs to take them? As an aside, I wonder if it would make some sense down the line to figure out how to "library-ize" this portion of SBCL core that is incorporated in OpenAxiom (and presumably also other stand-alone applications built using SBCL) so that it can be encapsulated and somehow packaged as an independent entity of its own that the various stand-alone applications depend on. Please note, I am _NOT_, in _ANY_ way, suggesting that this is something that *you* need to do for *this* package! That's fully out of scope for anything you should need to do, I'd think; I'm sure it's something that needs to be taken up by the upstream developers of SBCL and the various independent applications that are built using SBCL, and by the various major distributions as a whole (e.g. Debian, Ubuntu, Fedora/Red Hat, SUSE, maybe some of the others like Gentoo and Slackware, and by the non-Debians such as the various BSDs, OpenSolaris, etc), and possibly by the other major Lisps out there that are peers of SBCL (and which the independent applications might make use of instead of using SBCL). Again, thanks for your time. Hope this is of some use, interest. Joseph -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAC58tq-JSLMNyjmVRHwQFddSTXPzD=srh11g_sfevkjt3tp...@mail.gmail.com
