Some libraries like fullcalendar extract into directories like fullcalendar-1.5.3/fullcalendar/fullcalendar.js it would be nice if we could specify which directory to extract. Example fullcalendar-1.5.3/fullcalendar. This would also save from extra unnecessary code, like examples, from being installed also.

Comments

jgraham’s picture

jgraham commented

Related issue #1481158: how to deal with problem third party libraries?

dww’s picture

dww
we/he/they
commented

I think I'm in favor of this. We already support the ability to specify the location where things should be placed after extraction. Reading through #1481158: how to deal with problem third party libraries? it seems like it'd simplify things tremendously if .make file maintainers could just specify what part of the extracted directory tree to move into place. However, a few things to consider:

A) I'm not sure exactly how we'd specify this in the .make file, so suggested syntax would be very welcome.

B) This would complicate things a bit on the d.o packaging system if we extract only part of a library. It's harder to display that on the release nodes so folks know what happened. I guess they'd just have to inspect the .make file itself to find cases like this. Probably not a big deal, but I wanted to raise it. So long as the .make file itself is precise and results in reproducible builds, that's good enough. Just knowing a given library was included is already more than most end-users are going to care. Anyone who *really* wants to know exactly what happened can look in the .make file.

Thanks,
-Derek

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented

I think this is a duplicate of #919224: Allow use of subtrees or individual file from archives instead of the whole archive.

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (duplicate)

Yes, that's exactly the same feature. Great, thanks!