All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: autofs@linux.kernel.org
Subject: Re: [ANNOUNCE] autofs 5.0.0 beta2
Date: Thu, 18 May 2006 15:39:05 +0200	[thread overview]
Message-ID: <446C78F9.2080403@inria.fr> (raw)
In-Reply-To: <x49y7x12vml.fsf@redhat.com>

Jeff Moyer wrote:
> ==> Regarding Re: [autofs] [ANNOUNCE] autofs 5.0.0 beta2; Guillaume Rousse <Guillaume.Rousse@inria.fr> adds:
> 
> Guillaume.Rousse> Ian Kent wrote:
>>> Hi all,
>>>
>>> It's time for an updated beta.
>>>
>>> autofs ======
>>>
>>> The package can be found at:
>>>
>>> ftp://ftp.kernel.org/pub/linux/daemons/autofs/v5
>>>
>>> It is autofs-5.0.0_beta2.tar.[gz|bz2]
>>>
>>> No source rpm is there as it can be produced by using:
>>>
>>> rpmbuild -ts autofs-5.0.0_beta2.tar.gz
>>>
>>> and the binary rpm by using:
>>>
>>> rpmbuild -tb autofs-5.0.0_beta2.tar.gz
>>>
>>> See the INSTALL file for information about configure options and kernel
>>> requirements.
> Guillaume.Rousse> I couldn't test it really yet, as mandriva development
> Guillaume.Rousse> kernel is still 2.6.14, however here are a few remarks:
> 
> Guillaume.Rousse> First, stripping binaries by default, especially during
> Guillaume.Rousse> compilation, is opposite behaviour of standard
> Guillaume.Rousse> autotools-based procedure, where it only occurs if you
> Guillaume.Rousse> install with "make stripinstall". I need to have debug
> Guillaume.Rousse> symbols present when building a package, as they are
> Guillaume.Rousse> automatically for extracting them in a separate debug
> Guillaume.Rousse> package. I've found that "make DEBUG=1" would prevent
> Guillaume.Rousse> stripping, but it also defines an additional CFLAG with
> Guillaume.Rousse> unknown result :/
> 
> Try the attached patch.  It was made against the 4.1.3 Red Hat packages,
> but you get the idea.  Basically, "make -DDONTSTRIP."
I can achieve the same result without the patch with make CFLAGS="-O2 
-g" LDFLAGS="-g"  STRIP=":"
However, I find a bit cumbersome to need top pass arguments both to 
configure and to make invocation. And I wanted to point out it was not 
standard behaviour.

> Guillaume.Rousse> Second, the two attached patches don't apply anymore: -
> Guillaume.Rousse> autofs-4.1.4-signal-race-fix.patch seems to refer to
> Guillaume.Rousse> parts of automount.c not existing anymore -
> Guillaume.Rousse> autofs-4.1.1-get-best-mount.patch refer to a 4 args
> Guillaume.Rousse> get_best_mount() function that only has 3 args nowadays
> 
> Why would you apply 4.1.x patches to 5.x?  *Quite* a lot has changed.  I
> suggest dropping the patches.
Mainly because I don't know what they are meant for, I'm taking over 
package maintainership.

> Guillaume.Rousse> Third, the following patches still apply, but I got no
> Guillaume.Rousse> clue about their usefulness: -
> 
> Guillaume.Rousse> autofs-4.1.0-hesiod-bind.patch
> 
> I'll do some digging on this one tomorrow.
Thanks.

> Guillaume.Rousse> autofs-4.1.0-loop.patch
> 
> Drop this one.
OK.

  reply	other threads:[~2006-05-18 13:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 10:53 [ANNOUNCE] autofs 5.0.0 beta2 Ian Kent
2006-05-10 20:49 ` Guillaume Rousse
2006-05-17  2:45   ` Ian Kent
2006-05-17  2:57     ` Ian Kent
2006-05-18 13:39       ` Guillaume Rousse
2006-05-18 13:38     ` Guillaume Rousse
2006-05-17  3:11   ` Jeff Moyer
2006-05-18 13:39     ` Guillaume Rousse [this message]
2006-05-18 14:38       ` Jeff Moyer
2006-05-18 14:56         ` Guillaume Rousse
2006-05-19 13:31       ` Ian Kent
2006-05-19 13:33         ` Guillaume Rousse
2006-05-20  1:41           ` Ian Kent
2006-05-21 16:51             ` Guillaume Rousse
2006-05-26 22:56     ` Jeff Moyer
2006-05-27  3:08       ` Ian Kent
2006-05-27  8:13       ` Ian Kent
2006-05-27  9:25         ` Ian Kent
2006-05-27 17:26           ` Jeff Moyer

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=446C78F9.2080403@inria.fr \
    --to=guillaume.rousse@inria.fr \
    --cc=autofs@linux.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.