Re: Why no Class-Path manifest attribute?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/06/2014 11:54 AM, Florian Weimer wrote:
> On 02/06/2014 12:34 PM, Aleksandar Kurtakov wrote:
> 
>>> The spec file is here:
>>>
>>> <https://github.com/victims/victims-client-java/blob/master/victims-client-java.spec>
>>>
>>> As you can see, I use the usual Maven packaging framework.
>>
>> Bundling (and this is what your example is) is entirely forbidden - not just for Java but for everything.
>>
>> https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries
> 
> Even though Maven calls this dependency type "bundle", it is not 
> bundling in the sense of the quoted page.  The *sources* do not contain 
> copies of the library dependencies, neither in source form nor as 
> compiled classes.  The guidelines cited above deal with what is 
> contained in source RPMs—it does not even mention static linking.

I don't concur with your interpretation of that document.

It says that you can't bundle copies of libraries in packages.
Source RPMs are irrelevant here, as is static linking.

Andrew.

--
java-devel mailing list
java-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/java-devel





[Index of Archives]     [Red Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux