View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000635 | bareos-core | installer / packages | public | 2016-03-29 20:29 | 2016-05-05 21:34 |
Reporter | wandihuttel | Assigned To | |||
Priority | none | Severity | feature | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | Any | OS | Any | OS Version | Any |
Summary | 0000635: 16.1.0 - Compile from source make uninstall | ||||
Description | There's no option to remove bareos from source like bacula. make uninstall | ||||
Steps To Reproduce | ./configure \ --enable-smartalloc \ --with-mysql \ --with-db-user=bareos \ --with-db-password=bareos \ --with-db-port=3306 \ --with-readline=/usr/include/readline \ --sysconfdir=/etc \ --bindir=/sbin \ --sbindir=/sbin \ --with-scriptdir=/etc/bareos/scripts \ --with-plugindir=/etc/bareos/plugins \ --with-pid-dir=/etc/bareos/working \ --with-subsys-dir=/etc/bareos/working \ --with-working-dir=/etc/bareos/working \ --with-systemd \ --with-jansson \ --disable-conio \ --with-logdir=/var/log/bareos \ --disable-nls make -j 8 make install make uninstall | ||||
Tags | No tags attached. | ||||
The uninstall make target have been removed years ago, https://github.com/bareos/bareos/commit/a3a0be9fbb88bb0f4c660290bfafd984359d0ad9 Personally, I don't see the need to add it again. The preferred way is to work with packages. Otherwise you can still install Bareos to e.g. /opt/bareos and remove the whole directory if no longer needed. |
|
But in packages is not possible to change directories, change default configurations. I guess there's no sense to have a way to compile from source and doesn't have a way to uninstall. |
|
We decided to remove it as its error prone may remove stuff which are owned by packages etc. It also is extra effort to keep up to date etc. I don't know of many projects having uninstall targets and in packages you can do everything you say above as it installs to a so called staging area which you can modify in what ever way you like in either spec or deb files. Compiling from source is always available as that is the only way to create packages too. Further more if you use packages even self build ones the package manager will remove the files that actually belong to your package and not do some random removes. We also provide spec and deb files so if you really need something different you can use those as starting point to build your own packages. I guess the end conclusion is that we as project won't re-add those targets you are always free to fork the project and create your own version with those targets and keep that up to date to build your binaries from. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2016-03-29 20:29 | wandihuttel | New Issue | |
2016-03-30 13:28 | joergs | Note Added: 0002221 | |
2016-03-30 13:29 | joergs | Priority | normal => none |
2016-03-30 13:29 | joergs | Severity | major => feature |
2016-03-30 13:41 | wandihuttel | Note Added: 0002222 | |
2016-03-30 16:57 | mvwieringen | Note Added: 0002224 | |
2016-05-05 21:34 |
|
Status | new => closed |
2016-05-05 21:34 |
|
Resolution | open => no change required |