Opened 7 years ago

Closed 3 years ago

#34357 closed enhancement (fixed)

sqlgrey - make port independent on perl version installed

Reported by: BjarneDMat Owned by: pixilla (Bradley Giesbrecht)
Priority: Normal Milestone:
Component: ports Version:
Keywords: haspatch Cc: mojca (Mojca Miklavec)
Port: sqlgrey

Description

remove the dependency on perl5.12 and make it independent on which version of perl5 is installed.

Attachments (1)

patch-Portfile.diff (1.2 KB) - added by BjarneDMat 7 years ago.

Download all attachments as: .zip

Change History (6)

Changed 7 years ago by BjarneDMat

Attachment: patch-Portfile.diff added

comment:1 Changed 7 years ago by pixilla (Bradley Giesbrecht)

Cc: pixilla@… removed
Owner: changed from macports-tickets@… to pixilla@…

After installing sqlgrey, if perl5 is switched to a different perl there is no guarantee the perl modules sqlgrey depends on are present.

I think we will need to add subports or variants to sqlgrey for each perl version we want to support.

comment:2 Changed 7 years ago by BjarneDMat

hmmm ... wouldn't a 'port upgrade --force sqlgrey' (without -n) fix that problem?

I've just personally switched from perl 5.12 to perl 5.14 and did some nasty pieces of script to get updated:

port install perl5.14

port installed \
| grep p5.12 \
| while read portname version active
do
    port -f deactivate ${portname}
    port -f install ${portname/12/14}
done

# use perl5 port to switch to perl 5.14
# use cpan to initialise again
cpan
port -f uninstall perl5.12

( ( port installed \
| grep p5.12 \
| while read portname version active
do 
    port -q dependents ${portname}
done ) \
| sort \
| uniq \
| grep -v p5.12 ) |
xargs -n1 port -n upgrade --force 

# this is possibly overkill but resolved my problems with the modules looking for perl5.12 instaed of perl 5.14
cpan -l | while read module version
do
    cpan -f -i ${module}
done

comment:3 in reply to:  2 Changed 7 years ago by pixilla (Bradley Giesbrecht)

Replying to macintosh@…:

hmmm ... wouldn't a 'port upgrade --force sqlgrey' (without -n) fix that problem?

It is nice when stuff does not break in the first place :)

comment:4 Changed 3 years ago by mojca (Mojca Miklavec)

Cc: mojca@… added

Cc Me!

comment:5 Changed 3 years ago by mojca (Mojca Miklavec)

Resolution: fixed
Status: newclosed
Version: 2.0.4

This was addressed in r126932, r143202 (see also #48365).

Note: See TracTickets for help on using tickets.