You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So we already have an implementation of this in stackage-common but under slightly different superficial arguments. We'd like it updated to match the proposal (see end of ticket). Currently,
the two flag structure arguments are redundant, it can be just one. And the final action is remnant from fpbuild, it's really only used to determine whether the test suite or benchmarks are enabled. So these things can be put in a PackageConfig record data type (as below). It should just be a case of updating the places that need to be updated to enforce this API.
You can this along with your stackage-curator stuff and then pass to me and I'll port stackage-build to the latest stackage-common API and update anything as necessary.
--| Anything to do with a package associated with some directory.moduleStackage.PackagewheredataPackageExceptiondataPackage=Package{packageName::!PackageName
,packageVersion::!PackageVersion
,packageDir::!FilePath
,packageFiles::!(SetFilePath)
,packageDependencies::!(MapPackageNameVersionRange)
,packageTools::!(SetTool)
,packageFlags::!(MapTextBool)}dataBuildResultdataPackageConfig=PackageConfig{packageConfigEnableTests::!Bool
, packageConfigEnableBenchmarks::!Bool
, packageConfigFlags::!MapTextBool}readPackage:: (MonadLoggerm,MonadIOm,MonadThrowm)
=>PackageConfig->LocAbsoluteFile->mPackage
I've made the changes to Stackage.Package in commit 1b13a3d just to match the API for readPackage. Is PackageException a straight rename of FPException? And, I need details how what BuildResult should look like.
There are a few more functions in #1 that I haven't implemented/refactored
Is PackageException a straight rename of FPException?
Yep.
And, I need details how what BuildResult should look like.
The build/test/copy/register commands you can leave out (I purposely didn't include them in this ticket) unless you need them for your work right now. They will require extracting the code from stackage-build/src/Stackage/Build.hs, which is probably most efficient for me to do as I'm familliar with it and there's a lot of it. Made an issue for that in #6.
Activity
drwebb commentedon May 6, 2015
I've made the changes to
Stackage.Packagein commit 1b13a3d just to match the API forreadPackage. IsPackageExceptiona straight rename ofFPException? And, I need details how whatBuildResultshould look like.There are a few more functions in #1 that I haven't implemented/refactored
chrisdone commentedon May 6, 2015
Yep.
The
build/test/copy/registercommands you can leave out (I purposely didn't include them in this ticket) unless you need them for your work right now. They will require extracting the code fromstackage-build/src/Stackage/Build.hs, which is probably most efficient for me to do as I'm familliar with it and there's a lot of it. Made an issue for that in #6.drwebb commentedon May 7, 2015
Running this by you to see if this naming looks good. I can then merge and then mark this issue closed.
chrisdone commentedon May 7, 2015
Yep, nice!
drwebb commentedon May 7, 2015
done, closing