gxine

jlvsimoes · 2004-01-19 17:46:44

i builded gxine i like this gui for xine alot its here along with other useless stuff
http://routty.dhis.org/pkgs/feitos/gxine/

Mork II · 2004-01-19 22:14:15

This is beutiful! I mean really! Finally I will be able to purge my Xfce4-desktop from the horrors of xine-ui and xmms (and it's bastard child beep). The last bastation of plain ugly remaining is xpdf.

As a side note: Shouldn't gtk2 be listed as a dependency?

jlvsimoes · 2004-01-19 22:40:09

i relied on namcap to purge the dependencys so if gtk2 is a dependency namcap doest say so maybe someone without gtk2 " as if there is someone " can see if its ok like this

lanrat · 2004-01-20 01:27:47

Nice thing.
You could add this to the PKGBUILD

url="http://xinehq.de/"
md5sums=('d54af2f901065555348a77fa3b61581e')

My namcap says also:

gxine I: File (usr/share/gnome/apps/Multimedia/gxine.desktop) is a gnome menu item placed in the non-standard directory (should be opt/gnome/share/applications).
gxine E: Dependency detected and not included (gtk2)
gxine W: Dependency included but already satisfied (xfree86)
gxine W: Dependency included and not needed (ncurses)
gxine W: Dependency included and not needed (pkgconfig)
gxine W: Dependency included and not needed (curl)
gxine W: Dependency included and not needed (openssl)
gxine I: Depends as namcap sees them: depends=(xine-lib gtk2)

Locate also says that the other gnome .desktop files are in /opt/gnome/share/applications/
That's it for now. Maybe later I will be able to check it better.

Xentac · 2004-01-20 01:49:03

Geez... you guys take namcap's output as truth. That's just stupid.

Namcap probably won't give proper results on any machines that didn't compile the software (installed package list is very important).

The message about usr/share/gnome I'm not so sure about. That was partially a guess on my part. I'm pretty sure it works in either case.

Just remember that namcap is very stupid. The person running it is (hopefully) the smart one.

sarah31 · 2004-01-20 03:20:45

heh i was going to mention something along these lines too but not quite as harsh.

namcap is an aid not a replacement for research. you should do your best to find out what is needed as a depend without the need of namcap. as well namcap will not ALWAYS list necessary depends or unecessary depends.

Xentac · 2004-01-20 03:28:41

I try, but I keep seeing it over and over; people taking namcap's word for truth. I do my best, in as many places as possible, to explain that... but some people just don't listen.

It really gets to you when people use the tool you created incorrectly .

lanrat · 2004-01-20 10:00:39

No. I'm always using namcap only as an additional tool. And I built this package on my system first before running namcap.

The output about /opt/gnome/share is true. I've checked where the other .desktop files reside (with locate). The only .desktop files are in /opt/gnome/share and opt/kde/..... something. I did not have enough time to better check this PKGBUILD. I'll try to do this this week.

And to make this discussion more productive I'm asking what other steps do you take to make a new package?
Here is what I do (usually :-)):

1. Read the package homepage. Check documentation, forums, mailing lists, irc etc. Also check what google usenet search has to offer.

2. Download the source and untar it. Run ./configure --help. Check
with pacman -Ss for libraries etc. Make them first and install if they don't exist in the standard repos.

3. First simple edit of the standard PKGBUILD and run makepkg | tee pkgbuild.log.

4. Review the pkgbuild.log carefully to see what configure seeks, what it compiles in and what is needed to make the package (e.g. if there is no configure script and only autogen you may need to add automake to the build dependency list, I think). This is where pacman -Qo and pacman -Ql are very usefull.
EDIT: Review the files in src/ dir especially (if they exist) README, INSTALL, FAQ, NEWS, etc. There are some other output files from configure and make process that may be usefull. Sometimes interesting files may also be located in next subdir doc - this directory will be removed from binary package later according to AL standards!

5. Run namcap -i

7. Check what is the directory structure in pkg/ directory.

8. Edit the PKGBUILD and recompile if necessary.

9. Run makepkg -g >>PKGBUILD

10. Remake the package to be sure it works correctly.

11. Add package to the local repo, pacman -Syu, pacman -S.

12. Test the package.

I'm writing this from work without my AL machine so there may be some errors. I hope you will correct me :-)
Any other tips or tricks ?

jlvsimoes · 2004-01-20 14:22:41

http://routty.dhis.org/pkgs/feitos/gxin … pkg.tar.gz

pkgname=gxine
pkgver=0.3.3
pkgrel=2
url="http://xinehq.de/"
md5sums=('d54af2f901065555348a77fa3b61581e')
pkgdesc="A free video player for Unix"
depends=('gtk2' 'xine-lib')
source=(http://telia.dl.sourceforge.net/sourceforge/xine/gxine-$pkgver.tar.gz)

build() {
cd $startdir/src/gxine-$pkgver
./configure --prefix=/usr --with-x
make || return 1
make DESTDIR=$startdir/pkg install
}

thak you Mork II and larat i used ldd to figure the dependes now

sarah31 · 2004-01-20 16:10:37

that pretty well covers it lanrat. i do not do all those steps (ie maintaining a local repo).

Xentac · 2004-01-20 16:10:40

lanrat wrote:

5. Run namcap -i

I suggest running namcap on the final package you're going to submit, rather than sometime in the middle. Things can change significantly since then. You can also run namcap on the PKGBUILD.

lanrat · 2004-01-20 20:04:01

I will try namcap with PKGBUILD soon. We can also use some other distros and their repos to find out what may be missing in dependencies. I've found this for gxine:

http://rpmfind.net//linux/RPM/cooker/co … k.src.html
http://freshrpms.net/packages/builds/gxine/gxine.spec
http://www.gentoo-portage.com/browse-pr … ogram=3092
http://packages.debian.org/unstable/graphics/gxine
http://www.freebsd.org/cgi/ports.cgi?qu … &stype=all

Some pages include changelogs too. Sometimes package names are different but when you have sirious problems with compilation it may help a little. Some pages find more dependencies then the others - but in this case it's because the configure parameters are different (no support for lirc).

jlvsimoes · 2004-01-20 20:37:36

http://routty.dhis.org/pkgs/feitos/gxin … pkg.tar.gz

# Committer: jlvsimoes <jlvsimoes@oninet.pt>
pkgname=gxine
pkgver=0.3.3
pkgrel=3
url="http://xinehq.de/"
md5sums=('d54af2f901065555348a77fa3b61581e')
pkgdesc="A free video player for Unix"
depends=('gtk2' 'xine-lib')
source=(http://telia.dl.sourceforge.net/sourceforge/xine/gxine-$pkgver.tar.gz )

build() {
cd $startdir/src/gxine-$pkgver
./configure --prefix=/usr --with-x
make || return 1
make DESTDIR=$startdir/pkg install
mkdir -p $startdir/pkg/opt/gnome/share/applications/
mv $startdir/pkg/usr/share/gnome/apps/Multimedia/gxine.desktop $startdir/pkg/opt/gnome/share/applications/
}

nifan · 2004-01-20 21:01:30

when namcap "hit the road" i got the idea that it would help us a lot "developing" new packages to arch, and i quote man namcap:

namcap is a package analysis utility that looks for problems with arch-
linux packages or their PKGBUILD files. It can apply rules to the file
list, the files themselves, or individual PKGBUILD files.
Rules return lists of messages. Each message can be one of three
types: error, warning, or information (think of them as notes or com-
ments). Errors (designated by 'E:') are things that namcap is very
sure are wrong and need to be fixed. Warnings (designated by 'W:') are
things that namcap thinks should be changed but if you know what you're
doing then you can leave them. Information (designated 'I:') are only
shown when you use the info arguement. Information messages give
information that might be helpful but isn't anything that needs chang-
ing.

if it doesnt do the job that good, afterall if we still need to use ldd or whatever, namcap does only half the job its proposed to do, the part of resolving dependecies is not working as good as it sould. i'm not trying to be ofensive but thats the way i see things now. and i dont have much knoledge to develop packages.

Xentac · 2004-01-20 23:07:25

Namcap uses ldd to find the dependencies. There is no difference there.

If you do find a case where a dependency is incorrect, send me an email about it along with the package file and I'll look into it.

What makes namcap dumb is that it only uses ldd. If a C program uses dlopen(), namcap will never see it and the depends won't come out right. If a library is only linked to some obscure binary that is only used in certain other cases then namcap will think it is a dependency when it really isn't.

Anything that loads plugins, like gaim, uses dlopen().

An example of the latter is the old j2sdk and mozilla. The mozilla plugin is included in j2sdk but do you need mozilla to run java? Hardly. Namcap says that mozilla is a depenpency when, in reality, the only time you run into that need is when you already have mozilla installed.

Namcap is stupid because it tries to solve an extremely difficult problem systematically. It's not perfect and that's why I say it's stupid, because otherwise people think it has the final say.

PS: It's funny to see people quote the namcap man page to me... who do you think wrote it?

nifan · 2004-01-20 23:10:29

in that case the examples you've showed sould be in the man page. or something identical. thnkx for the explanation

lanrat · 2004-01-20 23:55:56

Don't underestimate The Dark Side of namcap :twisted:
But seriously namcap is still very usefull to me as it can quickly check long dependency chains (even if it is only running ldd). With bigger packages it's easy to forget to include some library in PKGBUILD. And this is the place where namcap is really helpfull (doublechecking). So it's not that stupid. (What is the IQ of namcap? :-))
AFAIK other distros also have the same problems. I tried to find something better than ldd googling around and couldn't find anything. It seems that everybody is doing this in the same way. Unfortunatelly not all distros have web interface to their repos with package building specifications. Or maybe there are some tools to ask some other (nonAL) repos about dependencies (something like pacman -Qi)? It would be nice to have some kind of additional "advisory" - in most cases someone already solved the problems with dependencies and we could use this knowledge. I mean of course that this is only in addition to normal procedure of building packages in AL. Just a thought....

EDIT:
..... and coming back to gxine. There still remains an empty directory.
I think PKGBUILD should include:

cd $startdir/pkg/usr/share
rmdir -p gnome/apps/Multimedia/

I run namcap -i on PKGBUILD and it says:

PKGBUILD (gxine) W: Missing Maintainer tag
PKGBUILD (gxine) W: Missing CVS Id tag

Is it ok?

There remains only one question about this package because it includes plugins for mozilla. I've found this: http://plugindoc.mozdev.org/linux.html
(under gxine):

Installation Instructions
Version: 0.3.3
1. Build and install gxine
2. Create symbolic links to the following files in your Mozilla plugins directory: gxineplugin.a gxineplugin.la gxineplugin.so

For standard mozilla the directory with plugins is
/opt/mozilla/lib/mozilla-1.5/plugins
and for firebird:
/opt/mozilla-firebird/lib/mozilla-1.5/plugins
Do we nedd to add this in AL for the plugins to work properly with mozilla?
Should PKGBUILD do something about this (postinstall?) or at least print this information after installation? What do you think?

jlvsimoes · 2004-01-22 22:37:35

gxine is in incoming

Xentac · 2004-01-23 01:30:49

lanrat wrote:

I run namcap -i on PKGBUILD and it says:
PKGBUILD (gxine) W: Missing Maintainer tag
PKGBUILD (gxine) W: Missing CVS Id tag
Is it ok?

This is ok. They are warnings because they're messages for developers only.

lanrat wrote:

There remains only one question about this package because it includes plugins for mozilla. I've found this: http://plugindoc.mozdev.org/linux.html
(under gxine):
Installation Instructions
Version: 0.3.3
1. Build and install gxine
2. Create symbolic links to the following files in your Mozilla plugins directory: gxineplugin.a gxineplugin.la gxineplugin.so
For standard mozilla the directory with plugins is
/opt/mozilla/lib/mozilla-1.5/plugins
and for firebird:
/opt/mozilla-firebird/lib/mozilla-1.5/plugins
Do we nedd to add this in AL for the plugins to work properly with mozilla?
Should PKGBUILD do something about this (postinstall?) or at least print this information after installation? What do you think?

You should probably do the same thing that the j2sdk package does: nothing. Some would argue that you should do like the flashplugin package does, but I don't really like that solution as it's not robust enough. Printing a message would probably work well too.

lanrat · 2004-01-23 11:49:40

Xentac wrote:

You should probably do the same thing that the j2sdk package does: nothing.

And that's exactly what I'll try to do. It's not an easy task, but I'll sacrifice myself

Xentac wrote:

Some would argue that you should do like the flashplugin package does, but I don't really like that solution as it's not robust enough. Printing a message would probably work well too.

I agree. Especially that the names of the subdirectories may change and I can't really ensure that the script will work with the next mozilla, firebird, etc. release. Printing a message with this link to mozilla page is enough I think. But first I'll try to test if this streaming works at all :?: And I had some problems with fullscreen mode after pressing f (in xfce4). It crashes sometimes. I'll let you know when I find something.

Michel · 2004-12-15 23:32:34

Heya,

it seems there was an update:

here is an updated PKGBUILD for it. This one works for me although on the commandline I get a lot of lines about redrawing, but it seems to work ...

PKGBUILD:

# Committer: jlvsimoes <jlvsimoes@oninet.pt>
# Contributor: Michel Brabants <michel.linux@tiscali.be>
pkgname=gxine
pkgver=0.4.1
pkgrel=1
url="http://xinehq.de/"
md5sums=('4a04df0d971a8952fb395b6eb0bc8dab')
pkgdesc="A free video player for Unix"
depends=('gtk2' 'xine-lib')
source=(http://belnet.dl.sourceforge.net/sourceforge/xine/$pkgname-$pkgver.tar.gz)

build() {
cd $startdir/src/gxine-$pkgver
./configure --prefix=/usr --with-x
make || return 1
make DESTDIR=$startdir/pkg install
#mkdir -p $startdir/pkg/opt/gnome/share/applications/
#mv $startdir/pkg/usr/share/gnome/apps/Multimedia/gxine.desktop $startdir/pkg/opt/gnome/share/applications/
}

matsche · 2004-12-20 00:10:21

the new version is out! i can compile it but it won't start!! :twisted: :evil: :evil:

Michel · 2004-12-20 13:09:50

Heya,

that's strange .. Can you post the error if possible?

Michel

matsche · 2004-12-20 17:24:51

hi
this is the error:

(gxine:3176): Gtk-WARNING **: Invalid input string

(gxine:3176): Gtk-WARNING **: Failed to set label from markup due to error parsi
ng markup: Fehler in Zeile 2, Zeichen 9: Ungültiger UTF-8-kodierter Text

** (gxine:3176): WARNING **: Invalid UTF8 string passed to pango_layout_set_text
()

I have this PKGBUILD:

# Contributor: matsche <matzeh@web.de>
# Maintainer: kritoke <kritoke@gamebox.net>

pkgname=gxine
pkgver=0.4.1
pkgrel=s1
url="http://xinehq.de/"
pkgdesc="A free video player for Unix"
depends=('gtk2' 'xine-lib')
source=(http://dl.sourceforge.net/sourceforge/xine/$pkgname-$pkgver.tar.gz )
md5sums=('4a04df0d971a8952fb395b6eb0bc8dab')

build() {
  cd $startdir/src/gxine-$pkgver
  ./configure --prefix=/usr --with-x
  make || return 1
  make DESTDIR=$startdir/pkg install
  mkdir -p $startdir/pkg/opt/gnome/share/applications/
}

:?:

Michel · 2004-12-21 16:56:13

Heya,

I updated the PKGBUILD. It seems to work for me ... and the PKGBUILD you used seems basically the same as the one I posted. Did you try updating all your libraries and then compile ?

Michel

Arch Linux

#1 2004-01-19 17:46:44

gxine

#2 2004-01-19 22:14:15

Re: gxine

#3 2004-01-19 22:40:09

Re: gxine

#4 2004-01-20 01:27:47

Re: gxine

#5 2004-01-20 01:49:03

Re: gxine

#6 2004-01-20 03:20:45

Re: gxine

#7 2004-01-20 03:28:41

Re: gxine

#8 2004-01-20 10:00:39

Re: gxine

#9 2004-01-20 14:22:41

Re: gxine

#10 2004-01-20 16:10:37

Re: gxine

#11 2004-01-20 16:10:40

Re: gxine

#12 2004-01-20 20:04:01

Re: gxine

#13 2004-01-20 20:37:36

Re: gxine

#14 2004-01-20 21:01:30

Re: gxine

#15 2004-01-20 23:07:25

Re: gxine

#16 2004-01-20 23:10:29

Re: gxine

#17 2004-01-20 23:55:56

Re: gxine

#18 2004-01-22 22:37:35

Re: gxine

#19 2004-01-23 01:30:49

Re: gxine

#20 2004-01-23 11:49:40

Re: gxine

#21 2004-12-15 23:32:34

Re: gxine

#22 2004-12-20 00:10:21

Re: gxine

#23 2004-12-20 13:09:50

Re: gxine

#24 2004-12-20 17:24:51

Re: gxine

#25 2004-12-21 16:56:13

Re: gxine

Board footer