Bug#458896: lintian: Wrong interpreter information w.r.t. pike
On lördagen den 5 januari 2008, Russ Allbery wrote: Magnus Holmgren [EMAIL PROTECTED] writes: lintian/checks/scripts currently lists pike, pike7, and pike7.6 as valid interpreters, associating them with packages of the same names. Currently, the available Pike interpreters are /usr/bin/pike7.6, provided by pike7.6-core, and /usr/bin/pike7.7, provided by pike7.7-core. /usr/bin/pike is managed by the alternatives system and could point to either - it should probably not be used by a packaged script. There are no scripts that would be compatible with multiple versions of Pike? Hmmm ... well, there probably exist such scripts, but they'd (theoretically) have to be able to work with all packages that can provide /usr/bin/pike, old as well as future, and that can't be guaranteed. Fortunately major Pike releases aren't very frequent... -- Magnus Holmgren signature.asc Description: This is a digitally signed message part.
Bug#458896: lintian: Wrong interpreter information w.r.t. pike
Magnus Holmgren [EMAIL PROTECTED] writes: On lördagen den 5 januari 2008, Russ Allbery wrote: There are no scripts that would be compatible with multiple versions of Pike? Hmmm ... well, there probably exist such scripts, but they'd (theoretically) have to be able to work with all packages that can provide /usr/bin/pike, old as well as future, and that can't be guaranteed. Fortunately major Pike releases aren't very frequent... I'm now treating pike like the other versioned scripts, which means that packages that use just /usr/bin/pike require a dependency on one or more of the known pike versions (currently pike7.6 | pike7.6-core | pike7.7 | pike7.7-core). It requires updating the known versions periodically, but the new structure should be much easier to maintain. And presumably if someone uses /usr/bin/pike and has a dependency on pike7.6 | pike7.7, they know what they're doing. The known versions list in lintian is *only* used for allowable dependencies for the unversioned interpreter. If you use /usr/bin/pike8.4 or something else lintian doesn't know about, it will assume that means you need a dependency on pike8.4 | pike8.4-core without needing to know about the version number in advance. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Bug#458896: lintian: Wrong interpreter information w.r.t. pike
Magnus Holmgren [EMAIL PROTECTED] writes: lintian/checks/scripts currently lists pike, pike7, and pike7.6 as valid interpreters, associating them with packages of the same names. Currently, the available Pike interpreters are /usr/bin/pike7.6, provided by pike7.6-core, and /usr/bin/pike7.7, provided by pike7.7-core. /usr/bin/pike is managed by the alternatives system and could point to either - it should probably not be used by a packaged script. There are no scripts that would be compatible with multiple versions of Pike? The previous maintainer was going to rename pike7.7 as pike7.8, which is what it will become when upstream releases it as stable, and I intend to follow that track soon. Pike needs a policy similar to Python's or Perl's with a default version, so things might change, but in the meantime, can you update Lintian in accordance with the above information? I'm going to completely overhaul how script dependencies are handled to try to lift more of the logic into data instead of code, and I'll fix this at the same time. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458896: lintian: Wrong interpreter information w.r.t. pike
Package: lintian lintian/checks/scripts currently lists pike, pike7, and pike7.6 as valid interpreters, associating them with packages of the same names. Currently, the available Pike interpreters are /usr/bin/pike7.6, provided by pike7.6-core, and /usr/bin/pike7.7, provided by pike7.7-core. /usr/bin/pike is managed by the alternatives system and could point to either - it should probably not be used by a packaged script. The previous maintainer was going to rename pike7.7 as pike7.8, which is what it will become when upstream releases it as stable, and I intend to follow that track soon. Pike needs a policy similar to Python's or Perl's with a default version, so things might change, but in the meantime, can you update Lintian in accordance with the above information? -- Magnus Holmgren New pike* (co)maintainer signature.asc Description: This is a digitally signed message part.
