On Sat, Mar 24, 2018 at 06:08:08PM -0500, Bruce Dubbs wrote:
>
> I certainly do not want to throw away what we have. I just do not want to
> go overboard with specifying every detail. By the time a user gets to the
> perl modules, he should have the ability to read the cpan output or perl
> messages when building to determine dependencies if needed.
>
> In the current case, we have an existing module that pulls in the needed
> dependent modules. Just specifying that is much easier from both the
> editors' point of view and the vast majority of the users' point of view. I
> merely want to prevent the perfect from getting in the way of good enough,
> especially if it creates more work for both.
>
> -- Bruce
>
Do you mean xref to (the dependencies of) LWP-Protocol-https ?
I guess I could live with that. Maybe I'm getting too close to the
perl modules ;)
I had similar thoughts about Falkon re the optional kwallet
dependency (that doesn't need *all* of kf5, but it needs enough of
it to only make the dep sensible if someone is already building
kde) - fortunately, I think Pierre took the ticket for that.
ĸen
--
Truth, in front of her huge walk-in wardrobe, selected black leather
boots with stiletto heels for such a barefaced truth.
- Unseen Academicals
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
