Paul Howarth wrote:
> It used to do:
> https://bugzilla.redhat.com/show_bug.cgi?id=1234563
That "bug" report is just totally backwards, this ought to be changed back
(and if other packages were similarly "improved", they need to be reverted,
too).
Kevin Kofler
__
Stephen John Smoogen wrote:
> Just say it.. no one wants to admit that emacs is needed for an OS to
> be operational :).
Yes, "an OS", the operating system Emacs. ;-) Any other OS can do just fine
without it. :-p
Kevin Kofler
___
devel mailing
On Fri, 21 Oct 2016 17:23:54 +0200
Kevin Kofler wrote:
> Tom Hughes wrote:
> > Because it's packaging some emacs extensions:
> >
> > % rpm -ql libidn.x86_64 | fgrep emacs
> > /usr/share/emacs/site-lisp/libidn
> > /usr/share/emacs/site-lisp/libidn/idna.el
> > /usr/share/emacs/site-lisp/libidn/idn
On Sat, 22 Oct 2016 01:24:57 +, Zbigniew Jędrzejewski-Szmek wrote:
> Probably better to just drop the -filesystem subpackage and make all dependent
> packages co-own that dir. Those -filesystem packages are a remnant of time
> before repoquery could be used to easily find all packages that use
On Fri, Oct 21, 2016 at 10:22:14PM +0100, Richard W.M. Jones wrote:
> On Fri, Oct 21, 2016 at 02:35:13PM +0530, Parag Nemade wrote:
> > and emacs package was added because of @core group
> > @core group installs iputils -> libidn -> emacs-filesystem
>
> Coincidentally when I was doing the RISC-V b
On Fri, Oct 21, 2016 at 02:35:13PM +0530, Parag Nemade wrote:
> and emacs package was added because of @core group
> @core group installs iputils -> libidn -> emacs-filesystem
Coincidentally when I was doing the RISC-V bring up, I really wished
that emacs-filesystem had been a separate package (or
Tom Hughes wrote:
> Because it's packaging some emacs extensions:
>
> % rpm -ql libidn.x86_64 | fgrep emacs
> /usr/share/emacs/site-lisp/libidn
> /usr/share/emacs/site-lisp/libidn/idna.el
> /usr/share/emacs/site-lisp/libidn/idna.elc
> /usr/share/emacs/site-lisp/libidn/punycode.el
> /usr/share/emac
On 21 October 2016 at 10:55, Zbigniew Jędrzejewski-Szmek
wrote:
> On Fri, Oct 21, 2016 at 02:23:47PM +0100, Peter Robinson wrote:
>> On Fri, Oct 21, 2016 at 2:21 PM, Zbigniew Jędrzejewski-Szmek
>> wrote:
>> > On Fri, Oct 21, 2016 at 01:31:25PM +0200, Jan Kratochvil wrote:
>> >> On Fri, 21 Oct 201
On Fri, Oct 21, 2016 at 02:23:47PM +0100, Peter Robinson wrote:
> On Fri, Oct 21, 2016 at 2:21 PM, Zbigniew Jędrzejewski-Szmek
> wrote:
> > On Fri, Oct 21, 2016 at 01:31:25PM +0200, Jan Kratochvil wrote:
> >> On Fri, 21 Oct 2016 13:18:38 +0200, Peter Robinson wrote:
> >> > guild would be because i
On Fri, Oct 21, 2016 at 2:21 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Fri, Oct 21, 2016 at 01:31:25PM +0200, Jan Kratochvil wrote:
>> On Fri, 21 Oct 2016 13:18:38 +0200, Peter Robinson wrote:
>> > guild would be because it's a dep of a dep of gdb-headless
>> guile
>>
>> libguile-2.0.so.22 is
On Fri, Oct 21, 2016 at 01:31:25PM +0200, Jan Kratochvil wrote:
> On Fri, 21 Oct 2016 13:18:38 +0200, Peter Robinson wrote:
> > guild would be because it's a dep of a dep of gdb-headless
> guile
>
> libguile-2.0.so.22 is DT_NEEDED - as shown by ldd.
>
> Easy way would be to make gdb-headless a
On Fri, 21 Oct 2016 13:18:38 +0200, Peter Robinson wrote:
> guild would be because it's a dep of a dep of gdb-headless
guile
libguile-2.0.so.22 is DT_NEEDED - as shown by ldd.
Easy way would be to make gdb-headless a separate binary/build.
Less easy way would be to dlopen() libguile from gdb a
On 21/10/16 12:18, Peter Robinson wrote:
Because they get pulled into builds for core deliverables. In the
case of emacs I believe it's because emacs-filesystem gets pulled in
due to libidn (I've no idea why libidn needs that and I'd love to get
that dep removed).
Because it's packaging some
On Fri, Oct 21, 2016 at 9:43 AM, Jan Synacek wrote:
> Why were critpath flags set on Emacs and Guile?
Because they get pulled into builds for core deliverables. In the
case of emacs I believe it's because emacs-filesystem gets pulled in
due to libidn (I've no idea why libidn needs that and I'd l
Hi,
On Fri, Oct 21, 2016 at 2:13 PM, Jan Synacek wrote:
> Why were critpath flags set on Emacs and Guile?
I think guile package was added because of @critical-path-base
@critical-path-base installs rpm-build -> gdb-headless -> guile
and emacs package was added because of @core group
@core group
Why were critpath flags set on Emacs and Guile?
Cheers,
--
Jan Synacek
Software Engineer, Red Hat
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
16 matches
Mail list logo