well pkgs with updatepod in a splitoff wouldn't be a pm, it's be something like net-snmp or a pkg with a perlmodule, now I'd rather split this into two info files, not everyone has taken that approach.
---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.

On 10-Dec-03, at 8:26 PM, Daniel Macks wrote:

Perhaps in a splitoff Type should be inheirited and a new _is_splitoff
key should be added (and decisions that used to be based on whether
_type=>splitoff would now look for _is_splitoff instead). I'm
currently hacking the Type processing code that does magical things
with 'perl' (branch type_langvers) so I could give that a try while
I'm there. OTOH, I'm going off-line for a few days in a couple of
hours, so I won't hurry it for this release (I don't want to tinker
with such a critical code chunk and leave everyone else to shake it
down and fix it up).

dan

On Wed, Dec 10, 2003 at 12:28:22PM -0700, TheSin wrote:
I haven't looked at the code or tested, but Type: perl in a split is
useless as type is for the buildprocess, splits aren't used till
install phase.

on the other hand updatePOD should be avail to splits but updatePOD now
uses type perl for the version. sorta chicken and the egg. so really
Type: perl should be allowed in splits but only to get the version if
UpdatePOD is used.

On 10-Dec-03, at 12:09 PM, Daniel Macks wrote:

The splitoff code suggests that a SplitOff can contain a Type, but the
Packaging Manual says type is present to "splitoff" and looking at
PkgVersion suggests that setting it to some other value breaks
things. But since type is clearly not inheirited, is there a problem
with splitoffs' UpdatePOD not getting special treatment for Type:
perl?



-- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks


Attachment: PGP.sig
Description: This is a digitally signed message part



Reply via email to