Opened 2 years ago

Closed 2 years ago

#5607 closed bug (fixed)

base is not trusted by default

Reported by: cdornan Owned by:
Priority: normal Milestone: 7.2.2
Component: Compiler Version: 7.2.1
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: None/Unknown Difficulty:
Test Case: Blocked By:
Blocking: Related Tickets:

Description

By default base doesn't appear to be trusted. I was asked to modify XHTML so that it would be trusted on post-7.0.1 compilers.

As a result XHTML won't compile on 7.2.1 out of the box and therefore hackage thinks it is broken and won't generate any Haddock markup.

I thought (and had been given to understand though the grapevine) that this was an oversight/bug in 7.2.1 but 7.2.2rc1 also has the same behavior.

So should base be trusted by default? If so then what about the sources of the core modules registered with hackage? Should they not be marked as trusted, or should the professed trustworthiness be put on a flag?

Change History (2)

comment:1 Changed 2 years ago by simonmar

  • Milestone set to 7.2.2

Let's make all packages trusted by default in 7.2.2.

comment:2 Changed 2 years ago by igloo

  • Resolution set to fixed
  • Status changed from new to closed

In the 7.2 branch, ghc-pkg will now mark all packages as trusted when they are installed.

commit 4a0378429439a9d5bd69816f0e4f2277da373d0f

Author: Ian Lynagh <igloo@earth.li>
Date:   Tue Nov 8 17:59:48 2011 +0000

    trust packages when they're installed
    
    For 7.2 we ignore the trust value in the package info we get given,
    and always trust packages
Note: See TracTickets for help on using tickets.