From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/4] libfm-extra: new package
Date: Tue, 25 Nov 2014 09:52:02 +0000 [thread overview]
Message-ID: <54745142.7040409@imgtec.com> (raw)
In-Reply-To: <20141124203345.474d71b1@free-electrons.com>
Dear Thomas Petazzoni,
On 11/24/2014 07:33 PM, Thomas Petazzoni wrote:
> Dear Vicente Olivert Riera,
>
> On Mon, 24 Nov 2014 10:10:50 +0000, Vicente Olivert Riera wrote:
>
>> On 11/22/2014 06:39 PM, Thomas Petazzoni wrote:
>>> Dear Vicente Olivert Riera,
>>>
>>> On Fri, 21 Nov 2014 15:33:07 +0000, Vicente Olivert Riera wrote:
>>>
>>>> +LIBFM_EXTRA_VERSION = 1.2.3
>>>> +LIBFM_EXTRA_SOURCE = libfm-$(LIBFM_EXTRA_VERSION).tar.xz
>>>
>>> This is the exact same tarball as the one used for the libfm package:
>>>
>>> +LIBFM_VERSION = 1.2.3
>>> +LIBFM_SOURCE = libfm-$(LIBFM_VERSION).tar.xz
>>> +LIBFM_SITE = http://sourceforge.net/projects/pcmanfm/files
>>>
>>> Why do we have two different packages? Is it because libfm full version
>>> needs menu-cache, and menu-cache needs libfm-extra?
>>
>> Yes, that is exactly the reason. Look for instance how is done in
>> LinuxFromScratch:
>>
>> http://www.linuxfromscratch.org/blfs/view/svn/lxde/libfm-extra.html
>>
>> They build libfm-extra first, then menu-cache and then libfm. I did
>> exactly the same.
>
> And you didn't explain that anywhere in the commit logs? No comments
> about this in the code? If you want such non-obvious stuff to be merged
> one day, you should at least add a little bit of explanation about it.
If you want, I don't mind to respin my patches adding more information
about that. But please, don't say that there is zero information because
in the "help" message of the libfm-extra package I added a short text
saying that package is needed for menu-cache:
+ help
+ The libfm-extra package contains a library and other files
+ required by menu-cache-gen libexec of menu-cache-1.0.0
And also in the cover-letter:
http://lists.busybox.net/pipermail/buildroot/2014-November/112652.html
> This all seems a bit crazy. How are the pcmanfm people building their
> stuff?
They are building it in that way. First libfm-extra, then menu-cache,
then libfm and finally pcmanfm.
Cheers,
--
Vicente Olivert Riera
Graduate Software Engineer, MIPS Processor IP
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com
next prev parent reply other threads:[~2014-11-25 9:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 15:33 [Buildroot] [PATCH v2 1/4] libfm-extra: new package Vicente Olivert Riera
2014-11-21 15:33 ` [Buildroot] [PATCH v2 2/4] menu-cache: " Vicente Olivert Riera
2014-12-10 21:05 ` Yann E. MORIN
2015-07-13 0:20 ` Thomas Petazzoni
2014-11-21 15:33 ` [Buildroot] [PATCH v2 3/4] libfm: " Vicente Olivert Riera
2014-12-10 21:18 ` Yann E. MORIN
2015-07-13 0:20 ` Thomas Petazzoni
2014-11-21 15:33 ` [Buildroot] [PATCH v2 4/4] pcmanfm: bump version to 1.2.3 Vicente Olivert Riera
2015-07-13 0:20 ` Thomas Petazzoni
2014-11-22 18:39 ` [Buildroot] [PATCH v2 1/4] libfm-extra: new package Thomas Petazzoni
2014-11-24 10:10 ` Vicente Olivert Riera
2014-11-24 19:33 ` Thomas Petazzoni
2014-11-25 9:52 ` Vicente Olivert Riera [this message]
2014-12-10 20:57 ` Yann E. MORIN
2014-12-10 21:10 ` Thomas Petazzoni
2014-12-10 21:28 ` Yann E. MORIN
2014-12-10 21:31 ` Thomas Petazzoni
2014-12-10 21:03 ` Yann E. MORIN
2015-07-13 0:19 ` Thomas Petazzoni
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=54745142.7040409@imgtec.com \
--to=vincent.riera@imgtec.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox