Hi On Mon, Dec 08, 2008 at 03:06:00PM +0100, Michal Čihař wrote: > Dne Sun, 7 Dec 2008 19:25:47 +0100 > Salvatore Bonaccorso <salvatore.bonaccorso@gmail.com> napsal(a): > > > The package can be found on mentors.debian.net: > > - URL: http://mentors.debian.net/debian/pool/main/t/tuxcmd > > - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free > > - dget http://mentors.debian.net/debian/pool/main/t/tuxcmd/tuxcmd_0.6.50-1.dsc > > Why is it only arch: i386 amd64? > > Also debian/copyright lacks some information: > - translation copyrights are not included > - also some source files have more than one copyright holders > > Using http://wiki.debian.org/Proposals/CopyrightFormat might be also a > good idea. I fix this issues when preparing to upload a new version to check, following the proposal, thanks! The reason I used only arch i386 and amd64, was bit "stupid" as I was not sure if the package would also build cleanly under the other architectures. See the note of the Author on: https://bugzilla.redhat.com/show_bug.cgi?id=449367 > Description says "Extendable via plugin system, several VFS modules > available in the distribution", while README.Debian "The tuxcmd > currently does not provide the additional plugins provided also > upstream, namely gnome_vfs, unrar_plugin and zip_plugin.". What is > problem in actually providing plugins? Yes I have to rephrase these sentences. The reason about that is the following: upstream ships the "base filemanager" tuxcmd in a source tarball, and in another tarball some modules (the above claimed, and I should rephrase the description for tuxcmd itself). For the modules I filled an separate ITP (see http://bugs.debian.org/508082). The second I have to repackage the upstream tarball to remove the "non free" module parts (unrar and libarchive plugin). Then tuxcmd-modules will "extend" tuxcmd by these additional modules. This second package tuxcmd-modules I have not yet ready to upload to mentors.debian.net, which then will extend the functionality of tuxcmd if installed. So that is what I ment or wanted to say in the README.Debian, but I should do better. "The tuxcmd package contains the base Tux Commander file manager. To extend the functionality using some VFS modules available you need to install the additional package tuxcmd-modules". Should explain the situation better. Since english is not my native language I should also post to the l10n-list, for checking the package description, for having best possible description. Is this a good approach to this? Or do you think it's still better to import also the "free" modules into the upstream source and repackage the tarball? I would upload a corrected package asap, and if ready since then, also the tuxcmd-modules package (if this is the right approach). Kind regards and thanks for checking Salvatore
Attachment:
signature.asc
Description: Digital signature