I've grown to prefer building RPMs (or to a lesser extent .debs).
Dependencies (RPM BuildRequires: or dpkg Build-Depends:) are explicitly
named. If you don't have them installed, you can't build.

Any magic steps that are necessary are documented in the packaging
file(s); you don't have to remember any extra steps.

It's easier to remove all the files that were installed. `make clean`
often doesn't get everything in my experience.

Building RPMs isn't for everyone though. It may be overkill for
developers. It's a good sanity check though for ops/devops that they
haven't overlooked something and as a bonus feature it's operationally
easier/better for install and upgrade.

Also the RPM building bits frequently add extra compile-time options
that developers don't always use; a good extra sanity check ahead of
packaging for Fedora and Ubuntu (to name two.)

My 2¢.

And having said all that, using STRICT_PACKAGE sounds like a good idea
to me.

--

Kaleb


On 03/22/2018 08:03 AM, Daniel Gryniewicz wrote:
> So, there is an option STRICT_PACKAGE that is supposed to enable this.
> It's not fully utilized, but it's mostly there.
> 
> The problem is that we can't tell whether the default is being used
> (lots of options are on by default but disable themselves if the
> packages aren't installed) or if the user explicitly turned them on.
> CMake doesn't seem to give us that information, that I've found.  So,
> instead, we have STRICT_PACKAGE, and you'll have to explicitly turn off
> everything that's on by default but that you don't want.
> 
> If you know of a better way of doing this, then I'm happy to listen and
> help implement it.
> 
> Daniel
> 
> On 03/22/2018 12:28 AM, Malahal Naineni wrote:
>> If I specify an option on the cmake command line, I would like it to
>> be honoured, if not, simply fail. Today,  cmake only gives a warning
>> if it can't meet my option's requirements. Can some cmake guru fix
>> this first?
>>
>> On Tue, Mar 20, 2018 at 8:38 PM, Daniel Gryniewicz <d...@redhat.com
>> <mailto:d...@redhat.com>> wrote:
>>
>>     It's probably a good idea to add the build options to --version
>>     output, or something.  That way we can ask for it in these types of
>>     situations.  I've added a card to the wishlist for this.
>>
>>     Daniel
>>
>>     On Tue, Mar 20, 2018 at 9:39 AM, TomK <tomk...@mdevsys.com
>>     <mailto:tomk...@mdevsys.com>> wrote:
>>      > On 3/19/2018 9:54 AM, Frank Filz wrote:
>>      >>>
>>      >>> Solved.
>>      >>>
>>      >>> Here's the solution in case it can help someone else.
>>      >>>
>>      >>> To get a certain feature in NFS Ganesha, I had to compile the
>> V2.6
>>      >>> release from source.  When configuring to compile, idmapd
>>     support got
>>      >>> disabled since packages were missing:
>>      >>>
>>      >>> libnfsidmap-devel-0.25-17.el7.x86_64
>>      >>>
>>      >>> Installed the above package and recompiled with nfsidmap
>>     support enabled
>>      >>> and this issue went away.  Users now show up properly off the
>>     NFS mount
>>      >>> on clients.
>>      >>
>>      >>
>>      >> Oh, well that was a simple fix :-)
>>      >>
>>      >> I wonder if we could make changes in our cmake files to make it
>>     easier to
>>      >> see when stuff got left out due to missing packages? I've been
>>     caught out
>>      >> myself.
>>      >>
>>      >> Frank
>>      >>
>>      > Yep, sure was an easy fix.
>>      >
>>      > Wouldn't mind seeing that.  Maybe even a way to find out what
>>     options went
>>      > into compiling packages for each distro.
>>      >
>>      >
>>      > --
>>      > Cheers,
>>      > Tom K.
>>      >
>>    
>> -------------------------------------------------------------------------------------
>>
>>      >
>>      > Living on earth is expensive, but it includes a free trip around
>>     the sun.
>>      >
>>
>>
> 
> 
> ------------------------------------------------------------------------------
> 
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Reply via email to