|
Message-ID: <20130903121429.GQ19628@janus.obspm.bsdfrog.org> Date: Tue, 3 Sep 2013 14:14:29 +0200 From: Antoine Jacoutot <ajacoutot@...frog.org> To: owl-users@...ts.openwall.com Subject: Re: MySQL w/cmake: anyone tried packaging for Owl? On Tue, Sep 03, 2013 at 04:05:25PM +0400, croco@...nwall.com wrote: > On Tue, Sep 03, 2013 at 12:47:02AM +0200, John Spencer wrote: > > On 09/02/2013 04:34 PM, Solar Designer wrote: > > > > >I did not test this with MySQL/MariaDB specifically, but in general: > > > > > >cmake -DCMAKE_INSTALL_PREFIX=/desired/target/dir > > BTW, I can confirm now that this doesn't work: the RPM is created > successfully, but after installation the configuration files contain the > file names such as /home/joe/.rpm.d/buildroots/mysql-5.5.33/usr/bin/mysql > and the like, and certainly all the mess can't start, as the files are > installed to /usr/bin, not /home/.../buildroots/.../usr/bin You may want to look at the Fedora spec file for MariaDB. There seem to be some useful hints and you can probably use the same for MySQL. extract: # The INSTALL_xxx macros have to be specified relative to CMAKE_INSTALL_PREFIX # so we can't use %%{_datadir} and so forth here. cmake . <...> -DINSTALL_LAYOUT=RPM -DCMAKE_INSTALL_PREFIX="%{_prefix}" <...> -DINSTALL_SCRIPTDIR=bin -- Antoine
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.