summaryrefslogtreecommitdiff
path: root/doc/forum/Adding_support_for_a_SQL_server/comment_1_6dc3fa35fb61bd53a5f5c88ea5bdbb45._comment
blob: 5376b576428f9dc4fb08a3bc2166c2bdef768f10 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
[[!comment format=mdwn
 username="joey"
 subject="""comment 1"""
 date="2018-06-12T14:38:22Z"
 content="""
We want to avoid adding heavy dependencies to propellor since that makes
propellor more expensive to bootstrap and adds a point of failure.

But, it should be easy enough to add dependencies to your own 
~/.propellor/config.cabal and write your properties using them. It would
also be fine to have additional libraries of propellor properties extending
propellor.

As for crypto hashes, it's certianly general enough to consider adding to
propellor, but it's also striking that propellor has mostly avoided needing
any hashes (except for some small uses of hashable and one place that
shells out to sha1). If there's a general purpose property that uses a
crypto hash, we could talk about adding it.
"""]]