Porting/corelist.pl does not set upstream=blead for enough

[p5pRT]

Migrated from rt.perl.org#126235 (status was 'open')

Searchable as RT126235$

[p5pRT]

From @rjbs

Created by @rjbs

The modules "if" and "strict" and "warnings" don't show up in %Module​::CoreList​::upstream. If added by hand\, they're removed when Porting/corelist.pl is run. Porting/corelist.pl should be updated to include core code as upstream blead.

While maybe "strict" and "warnings" as non-dual-life modules should remain undef (although I'm dubious of this)\, "if" is dual-life with upstream blead\, and should be reflected as such.

It wasn't immediately clear to me howt his gets sorted out\, so for now I'm just filing the ticket.

Perl Info

``` Flags: category=library severity=medium module=Module::CoreList Site configuration information for perl 5.23.3: Configured by rjbs at Mon Sep 21 11:54:00 EDT 2015. Summary of my perl5 (revision 5 version 23 subversion 3) configuration: Platform: osname=darwin, osvers=14.5.0, archname=darwin-2level uname='darwin jubjub.local 14.5.0 darwin kernel version 14.5.0: wed jul 29 02:26:53 pdt 2015; root:xnu-2782.40.9~1release_x86_64 x86_64 ' config_args='-Dprefix=/Users/rjbs/.plenv/versions/23.3 -de -Dusedevel -A'eval:scriptdir=/Users/rjbs/.plenv/versions/23.3/bin'' hint=recommended, useposix=true, d_sigaction=define useithreads=undef, usemultiplicity=undef use64bitint=define, use64bitall=define, uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='cc', ccflags ='-fno-common -DPERL_DARWIN -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -I/opt/local/include', optimize='-O3', cppflags='-fno-common -DPERL_DARWIN -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -I/opt/local/include' ccversion='', gccversion='4.2.1 Compatible Apple LLVM 7.0.0 (clang-700.0.72)', gccosandvers='' intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678, doublekind=3 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16, longdblkind=3 ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=8, prototype=define Linker and Libraries: ld='env MACOSX_DEPLOYMENT_TARGET=10.3 cc', ldflags =' -fstack-protector-strong -L/usr/local/lib -L/opt/local/lib' libpth=/usr/local/lib /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/7.0.0/lib /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib /usr/lib /opt/local/lib libs=-lpthread -lgdbm -ldbm -ldl -lm -lutil -lc perllibs=-lpthread -ldl -lm -lutil -lc libc=, so=dylib, useshrplib=false, libperl=libperl.a gnulibc_version='' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=bundle, d_dlsymun=undef, ccdlflags=' ' cccdlflags=' ', lddlflags=' -bundle -undefined dynamic_lookup -L/usr/local/lib -L/opt/local/lib -fstack-protector-strong' @INC for perl 5.23.3: /Users/rjbs/.plenv/versions/23.3/lib/perl5/site_perl/5.23.3/darwin-2level /Users/rjbs/.plenv/versions/23.3/lib/perl5/site_perl/5.23.3 /Users/rjbs/.plenv/versions/23.3/lib/perl5/5.23.3/darwin-2level /Users/rjbs/.plenv/versions/23.3/lib/perl5/5.23.3 . Environment for perl 5.23.3: DYLD_LIBRARY_PATH (unset) HOME=/Users/rjbs LANG=en_US.UTF-8 LANGUAGE (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=/Users/rjbs/.plenv/versions/23.3/bin:/Users/rjbs/.plenv/libexec:/Users/rjbs/.plenv/plugins/perl-build/bin:/Users/rjbs/bin:/Users/rjbs/.rbenv/shims:/Users/rjbs/.rbenv/bin:/Users/rjbs/.rakudobrew/bin:/Users/rjbs/.plenv/shims:/Users/rjbs/.plenv/bin:/opt/local/bin:/opt/local/sbin:/usr/local/texlive/2015/bin/x86_64-darwin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/Users/rjbs/code/hla PERLDOC=-otext PERL_AUTOINSTALL=--skipdeps PERL_BADLANG (unset) PERL_MAILERS=sendmail:/Users/rjbs/bin/sendmail SHELL=/opt/local/bin/zsh ```

[p5pRT]

From @karenetheridge

On Thu Oct 01 04​:23​:52 2015\, rjbs wrote​:

While maybe "strict" and "warnings" as non-dual-life modules should remain undef (although I'm dubious of this)\, "if" is dual-life with upstream blead\, and should be reflected as such.

(For other toolchainy code) I've wanted for quite some time an interface that will tell me if a core module is dual-lifed or not. I'd find it quite acceptable for the "what is upstream?" query to return undef for non-dual-lifed modules\, as obviously blead is the only place such a module can live.

[p5pRT]

The RT System itself - Status changed from 'new' to 'open'