Re: Removing non-Linux files from source tarballs
On 11/6/07, Jordi Gutiérrez Hermoso [EMAIL PROTECTED] wrote: So remove them either way? Yep, especially, since you will be creating the orig.tar.gz from upstream SVN (and writing a debian/rules get-orig-source target), instead of just distributing their tarball. -- bye, pabs http://wiki.debian.org/PaulWise
Re: Removing non-Linux files from source tarballs
On 01/11/2007, Paul Wise [EMAIL PROTECTED] wrote: On 11/2/07, Jordi Gutiérrez Hermoso [EMAIL PROTECTED] wrote: Now, Processing distributes in its source tarball (well, not really a source tarball at all, since it's necessary to get everything from svn), some Windows .exes and some MacOSX-specific files too. Do these have to be removed from the source package that I make for Debian? If there is no source for them in the tarball, yes. If there is source in the tarball, I'd suggest that it is worth the space saving to remove them. So remove them either way? They seem to be various version of the JRE for Windows and MacOS X plus the binary for some graphical Windows installer. I don't know how MacOS X distributes binaries at all, so I don't understand what the MacOS X directory of Processing contains, although file(1) tells me it's all binary, and there's no source in sight. On 02/11/2007, Justin Pryzby [EMAIL PROTECTED] wrote: On Thu, Nov 01, 2007 at 04:27:14PM -0600, Jordi Gutiérrez Hermoso wrote: It would save 20 megs from the source package. Is that considerable enough for their removal? That part isn't in policy :) Is that 20mb before or after compression? After compression. The big ones are mostly jre.zip and jre.tgz for Windows and GNU/Linux respectively. There are a few other files such as the graphical Windows installer that I mentioned above that adds about 3 more megs after compression. And get upstream a clue :) I am nagging upstream about this useless .txt extension they seem to favour (preferences.txt, ugh!) and about having executable permissions set on other text files (e.g. on a Makefile without a /usr/bin/make shebang!). Their build process is also downright ugly. It's a shell script that attempts to mimic a Makefile and does everything manually. There's been talk about moving the build process to Apache Ant, but upstream tells me this is low priority. I guess when you create code for Windows and MacOS X, professional deformation makes you do some relatively silly things for GNU/Linux. :-) - Jordi G. H.
Re: Removing non-Linux files from source tarballs
On Thu, Nov 01, 2007 at 04:27:14PM -0600, Jordi Gutiérrez Hermoso wrote: On 01/11/2007, Justin Pryzby [EMAIL PROTECTED] wrote: On Thu, Nov 01, 2007 at 01:17:26PM -0600, Jordi Gutiérrez Hermoso wrote: Hello, mentors. I'm currently working on Processing (#433270). Now, Processing distributes in its source tarball (well, not really a source tarball at all, since it's necessary to get everything from svn), some Windows .exes and some MacOSX-specific files too. Do these have to be removed from the source package that I make for Debian? I forget if it's policy or devref which prefers *not* removing them unless you're already using a nonpristine sourceball or it would save significant space, It would save 20 megs from the source package. Is that considerable enough for their removal? That part isn't in policy :) Is that 20mb before or after compression? Since it's a source package, there's only one copy (per suite, perhaps with a couple extra copies for a couple days at a time [?], but not per architecture). If you do repackage, make sure to provide an get-orig-source target to retrieve (?), unpack, modify, and repack that (and the top level dir should have .orig appended). Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Removing non-Linux files from source tarballs
Hello, mentors. I'm currently working on Processing (#433270). Now, Processing distributes in its source tarball (well, not really a source tarball at all, since it's necessary to get everything from svn), some Windows .exes and some MacOSX-specific files too. Do these have to be removed from the source package that I make for Debian? Processing also distributes its own Java and Jikes compilers, and of course those have to be removed. I'll need to patch the build process in order to make sure that it will work with Debian's versions of these packages. Oh, and it looks like it'll have to go into contrib, until Java becomes completely free. :-/ Confirm, deny? Thanks, - Jordi G. H. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Removing non-Linux files from source tarballs
On Thu, Nov 01, 2007 at 01:17:26PM -0600, Jordi Gutiérrez Hermoso wrote: Hello, mentors. I'm currently working on Processing (#433270). Now, Processing distributes in its source tarball (well, not really a source tarball at all, since it's necessary to get everything from svn), some Windows .exes and some MacOSX-specific files too. Do these have to be removed from the source package that I make for Debian? I forget if it's policy or devref which prefers *not* removing them unless you're already using a nonpristine sourceball or it would save significant space, (with the justification that people might like to use the debian sources for nondebian things) Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Removing non-Linux files from source tarballs
On Thu, 1 Nov 2007 13:17:26 -0600, Jordi Gutiérrez Hermoso [EMAIL PROTECTED] said: Hello, mentors. I'm currently working on Processing (#433270). [...] Oh, and it looks like it'll have to go into contrib, until Java becomes completely free. :-/ Confirm, deny? See if it works with, e.g. gij + classpath. Otherwise, yes, it will have to go into contrib. -- Hubert Chathi [EMAIL PROTECTED] -- Jabber: [EMAIL PROTECTED] PGP/GnuPG key: 1024D/124B61FA http://www.uhoreg.ca/ Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Removing non-Linux files from source tarballs
On 01/11/2007, Justin Pryzby [EMAIL PROTECTED] wrote: On Thu, Nov 01, 2007 at 01:17:26PM -0600, Jordi Gutiérrez Hermoso wrote: Hello, mentors. I'm currently working on Processing (#433270). Now, Processing distributes in its source tarball (well, not really a source tarball at all, since it's necessary to get everything from svn), some Windows .exes and some MacOSX-specific files too. Do these have to be removed from the source package that I make for Debian? I forget if it's policy or devref which prefers *not* removing them unless you're already using a nonpristine sourceball or it would save significant space, It would save 20 megs from the source package. Is that considerable enough for their removal? - Jordi G. H.
Re: Removing non-Linux files from source tarballs
On 01/11/2007, Hubert Chathi [EMAIL PROTECTED] wrote: On Thu, 1 Nov 2007 13:17:26 -0600, Jordi Gutiérrez Hermoso [EMAIL PROTECTED] said: Hello, mentors. I'm currently working on Processing (#433270). [...] Oh, and it looks like it'll have to go into contrib, until Java becomes completely free. :-/ Confirm, deny? See if it works with, e.g. gij + classpath. Otherwise, yes, it will have to go into contrib. I haven't been able to make it work with anything but Sun's Java. The upstream authors confirm this. - Jordi G. H.
Re: Removing non-Linux files from source tarballs
On 11/2/07, Jordi Gutiérrez Hermoso [EMAIL PROTECTED] wrote: Now, Processing distributes in its source tarball (well, not really a source tarball at all, since it's necessary to get everything from svn), some Windows .exes and some MacOSX-specific files too. Do these have to be removed from the source package that I make for Debian? If there is no source for them in the tarball, yes. If there is source in the tarball, I'd suggest that it is worth the space saving to remove them. Since you are manually creating the orig.tar.gz from SVN anyway, obviously leave them out since they are not source code. And add a get-orig-source target to recreate the tarball automatically. And get upstream a clue :) -- bye, pabs http://wiki.debian.org/PaulWise
