Bug #41668 It is not possible to use backup stream library outside sql/backup
Submitted: 22 Dec 2008 11:32 Modified: 10 Sep 12:04
Reporter: Rafal Somla
Status: Won't fix
Category:Server: Backup Severity:S4 (Feature request)
Version:6.0 source OS:Any
Assigned to: Chuck Bell Target Version:
Tags: teamtree
Triage: Triaged: D5 (Feature request)

[22 Dec 2008 11:32] Rafal Somla 
Description:
The backup stream library (sql/backup/libbackupstream.la) is meant to be a portable
interface for reading and writing backup images. For example the backup client, to be
implemented by WL#4534/WL#4630, should use this library to read backup files.

However, since the library lives in sql/backup, it is not possible to use it in a client
which lives in client/ dir and is compiled before the library is built.

The workaround used in the client is to symlink and use library sources directly for
building the application. But a cleaner solution would be to use already compiled library
which was the original intention.

How to repeat:
Code inspection.

Suggested fix:
Do the following things.

1. Move library sources (currently sql/backup/stream_v1.c and
sql/backup/stream_v1_transport.c) to some location where it will be compiled early in the
build process (porbably to extra/ or libmysqld/)

2. "Publish" the library's public headers (stream_v1.h and stream_v1_services.h) by
moving them to some directory which is searched during build process (probably include/)
[10 Sep 12:04] Lars Thalmann 
Even though this would be nice, I don't see this having 
high prio in the next 2-3 years.  Closing as "Won't fix".

It we later decide to do this, we can always re-open the bug report, 
but for now it does not make sense to spend time administrating 
this report as open.