On 8 Apr 2010, at 22:02, Greg Stein wrote:
> Hey all,
>
> It has come up a few times on IRC discussions: "we should never have
> exposed libsvn_wc, just libsvn_client".
>
> Well, we've already exposed it, so we need to at least keep that stuff
> around. But moving forward... should new functions continue to be
> exposed? Or should all new functions go into svn_wc_private.h?
>
> This question is (probably) directed at our (GUI) client developers.
> Do you ever use WC functions? And if you do, then which ones? Where is
> svn_client.h insufficient, leading you to use svn_wc.h APIs?
>
> Note: I think the separation is a Good Thing, for our benefit, but we
> don't necessarily have to expose the WC layer to downstream
> developers.
>
> Cheers,
> -g
Here are the list of svn_wc_ symbols from pysvn.
pysvn does not include svn_wc.h.
svn_wc_adm_access_t
svn_wc_adm_probe_open
svn_wc_adm_probe_open3
svn_wc_conflict_action_add
svn_wc_conflict_action_delete
svn_wc_conflict_action_edit
svn_wc_conflict_action_t
svn_wc_conflict_choice_t
svn_wc_conflict_choose_base
svn_wc_conflict_choose_merged
svn_wc_conflict_choose_mine_conflict
svn_wc_conflict_choose_mine_full
svn_wc_conflict_choose_postpone
svn_wc_conflict_choose_theirs_conflict
svn_wc_conflict_choose_theirs_full
svn_wc_conflict_description_t
svn_wc_conflict_kind_property
svn_wc_conflict_kind_t
svn_wc_conflict_kind_text
svn_wc_conflict_reason_deleted
svn_wc_conflict_reason_edited
svn_wc_conflict_reason_missing
svn_wc_conflict_reason_obstructed
svn_wc_conflict_reason_t
svn_wc_conflict_reason_unversioned
svn_wc_conflict_result_t
svn_wc_conflict_version_t
svn_wc_create_conflict_result
svn_wc_dup_status
svn_wc_dup_status2
svn_wc_entry
svn_wc_entry_t
svn_wc_get_adm_dir
svn_wc_info_dup
svn_wc_info_t
svn_wc_is_adm_dir
svn_wc_merge_conflict
svn_wc_merge_merged
svn_wc_merge_no_merge
svn_wc_merge_outcome_t
svn_wc_merge_unchanged
svn_wc_notify_action_t
svn_wc_notify_add
svn_wc_notify_blame_revision
svn_wc_notify_changelist_clear
svn_wc_notify_changelist_moved
svn_wc_notify_changelist_set
svn_wc_notify_commit_added
svn_wc_notify_commit_deleted
svn_wc_notify_commit_modified
svn_wc_notify_commit_postfix_txdelta
svn_wc_notify_commit_replaced
svn_wc_notify_copy
svn_wc_notify_delete
svn_wc_notify_exists
svn_wc_notify_failed_external
svn_wc_notify_failed_lock
svn_wc_notify_failed_revert
svn_wc_notify_failed_unlock
svn_wc_notify_foreign_merge_begin
svn_wc_notify_locked
svn_wc_notify_merge_begin
svn_wc_notify_merge_completed
svn_wc_notify_property_added
svn_wc_notify_property_deleted
svn_wc_notify_property_deleted_nonexistent
svn_wc_notify_property_modified
svn_wc_notify_resolved
svn_wc_notify_restore
svn_wc_notify_revert
svn_wc_notify_revprop_deleted
svn_wc_notify_revprop_set
svn_wc_notify_skip
svn_wc_notify_state_changed
svn_wc_notify_state_conflicted
svn_wc_notify_state_inapplicable
svn_wc_notify_state_merged
svn_wc_notify_state_missing
svn_wc_notify_state_obstructed
svn_wc_notify_state_t
svn_wc_notify_state_unchanged
svn_wc_notify_state_unknown
svn_wc_notify_status_completed
svn_wc_notify_status_external
svn_wc_notify_t
svn_wc_notify_tree_conflict
svn_wc_notify_unlocked
svn_wc_notify_update_add
svn_wc_notify_update_completed
svn_wc_notify_update_delete
svn_wc_notify_update_external
svn_wc_notify_update_replace
svn_wc_notify_update_update
svn_wc_operation_merge
svn_wc_operation_none
svn_wc_operation_switch
svn_wc_operation_t
svn_wc_operation_update
svn_wc_schedule_add
svn_wc_schedule_delete
svn_wc_schedule_normal
svn_wc_schedule_replace
svn_wc_schedule_t
svn_wc_set_adm_dir
svn_wc_status2_t
svn_wc_status_added
svn_wc_status_conflicted
svn_wc_status_deleted
svn_wc_status_external
svn_wc_status_ignored
svn_wc_status_incomplete
svn_wc_status_kind
svn_wc_status_merged
svn_wc_status_missing
svn_wc_status_modified
svn_wc_status_none
svn_wc_status_normal
svn_wc_status_obstructed
svn_wc_status_replaced
svn_wc_status_t
svn_wc_status_unversioned
Barry
Received on 2010-05-16 11:00:49 CEST