Summary: | media-libs/libdvdcss - small syntax issue with libdvdcss-1.2.9-r1 ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | sam logen <starz909> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED INVALID | ||
Severity: | trivial | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
sam logen
2008-01-10 04:02:58 UTC
Why? It completely doesn't matter where the quoting is closed. (Patches for xine should be submitted upstream.) (In reply to comment #1) > Why? It completely doesn't matter where the quoting is closed. > > (Patches for xine should be submitted upstream.) > Well I didn't know that. The Gentoo Howto on overlays and ebuild files shows the syntax of ebuild files, so I naturally assumed this was a typo, and out of the goodness of my heart, I decided to bring it to people's attention. By the way, what does "Upstream" mean? If that has something to do with the patch I was talking about, it's not for xine. It's FROM xine. I was just curious if anyone wanted people to have the option of enabling the network capability of libdvdcss with the patch from the xine developers. (In reply to comment #2) > (In reply to comment #1) > Well I didn't know that. The Gentoo Howto on overlays and ebuild files shows > the syntax of ebuild files, so I naturally assumed this was a typo, and out of > the goodness of my heart, I decided to bring it to people's attention. Well thanks, but this really isn't a bug. The quoting is there for cases when people put PORTDIR into a path which contains spaces for whatever whacky reason. You can easily test this with something like: foo="/tmp/stupid path with spaces"; mkdir -p "${foo}"; touch "${foo}/foo.txt" foo="/tmp/stupid path with spaces"; mkdir -p "${foo}"; touch "${foo}"/foo.txt and see that the quoting works as expected in both cases. > By the way, what does "Upstream" mean? If that has something to do with the > patch I was talking about, it's not for xine. It's FROM xine. Misunderstood you then. Anyway, a separate bug please, it's completely unrelated to the original topic. |