From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH proxmox-backup-qemu] build: track symbols
Date: Tue, 9 Feb 2021 12:29:33 +0100 [thread overview]
Message-ID: <20210209112933.2654904-2-f.gruenbichler@proxmox.com> (raw)
In-Reply-To: <20210209112933.2654904-1-f.gruenbichler@proxmox.com>
for easier auto-generation of versioned deps. when adding new symbols,
the build should display a warning + diff (in addition to our manual
tracking of the generated header file). changes in symbol signatures or
semantics are not caught automatically by the symbols file, but still
require bumping the minimum library version for that symbol accordingly.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
this reflects the current state in master - the masterkey patch changes
proxmox_backup_new to 1.0.3 or whatever the post-bump version is..
debian/libproxmox-backup-qemu0.symbols | 34 ++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
create mode 100644 debian/libproxmox-backup-qemu0.symbols
diff --git a/debian/libproxmox-backup-qemu0.symbols b/debian/libproxmox-backup-qemu0.symbols
new file mode 100644
index 0000000..603235a
--- /dev/null
+++ b/debian/libproxmox-backup-qemu0.symbols
@@ -0,0 +1,34 @@
+libproxmox_backup_qemu.so.0 libproxmox-backup-qemu0 #MINVER#
+ proxmox_backup_abort@Base 1.0.0
+ proxmox_backup_add_config@Base 1.0.0
+ proxmox_backup_add_config_async@Base 1.0.0
+ proxmox_backup_check_incremental@Base 1.0.0
+ proxmox_backup_close_image@Base 1.0.0
+ proxmox_backup_close_image_async@Base 1.0.0
+ proxmox_backup_connect@Base 1.0.0
+ proxmox_backup_connect_async@Base 1.0.0
+ proxmox_backup_disconnect@Base 1.0.0
+ proxmox_backup_finish@Base 1.0.0
+ proxmox_backup_finish_async@Base 1.0.0
+ proxmox_backup_free_error@Base 1.0.0
+ proxmox_backup_new@Base 1.0.0
+ proxmox_backup_qemu_version@Base 1.0.2
+ proxmox_backup_register_image@Base 1.0.0
+ proxmox_backup_register_image_async@Base 1.0.0
+ proxmox_backup_snapshot_string@Base 1.0.0
+ proxmox_backup_write_data@Base 1.0.0
+ proxmox_backup_write_data_async@Base 1.0.0
+ proxmox_export_state@Base 1.0.0
+ proxmox_free_state_buf@Base 1.0.0
+ proxmox_import_state@Base 1.0.0
+ proxmox_restore_connect@Base 1.0.0
+ proxmox_restore_connect_async@Base 1.0.0
+ proxmox_restore_disconnect@Base 1.0.0
+ proxmox_restore_get_image_length@Base 1.0.0
+ proxmox_restore_image@Base 1.0.0
+ proxmox_restore_new@Base 1.0.0
+ proxmox_restore_open_image@Base 1.0.0
+ proxmox_restore_open_image_async@Base 1.0.0
+ proxmox_restore_read_image_at@Base 1.0.0
+ proxmox_restore_read_image_at_async@Base 1.0.0
+ (optional)rust_eh_personality@Base 1.0.0
--
2.20.1
next prev parent reply other threads:[~2021-02-09 11:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 11:29 [pve-devel] [PATCH qemu] build: drop explicit libproxmox-backup-qemu0 dep Fabian Grünbichler
2021-02-09 11:29 ` Fabian Grünbichler [this message]
2021-02-12 14:35 ` [pve-devel] applied: [PATCH proxmox-backup-qemu] build: track symbols Thomas Lamprecht
2021-02-12 14:36 ` [pve-devel] applied: [PATCH qemu] build: drop explicit libproxmox-backup-qemu0 dep Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210209112933.2654904-2-f.gruenbichler@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox