Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#13533 - libflashsupport-oss source is unavailable

Attached to Project: Community Packages
Opened by Greg (dolby) - Thursday, 26 February 2009, 10:37 GMT
Last edited by Paulo Matias (thotypous) - Saturday, 21 March 2009, 15:56 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Paulo Matias (thotypous)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

libflashsupport-oss source is unavailable
http://aur.archlinux.org/packages.php?ID=20327
This task depends upon

Closed by  Paulo Matias (thotypous)
Saturday, 21 March 2009, 15:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  libflashsupport-oss package was removed and merged back in oss-4.1_1051-3.
Comment by Greg (dolby) - Saturday, 28 February 2009, 14:50 GMT
Seems its just oudated. http://www.4front-tech.com/developer/sources/stable/gpl/oss-v4.1-build1051-src-gpl.tar.bz2
Yet another project that doesnt keep the sources of previous versions available.
Comment by Paulo Matias (thotypous) - Saturday, 28 February 2009, 15:06 GMT
Well, it's not outdated because no changes have been made to libflashsupport itself since them.

But updating libflashsupport-oss every time oss is updated would be a waste of resources (in the sense it is not needed).

To have sources available, we could just include the only one C source file that composes the package in our CVS, or otherwise host this file elsewhere.

Another way to solve this problem would be to merge libflashsupport-oss back in the same package as oss. It was splitted in a separate package in the past only because there was no flash player for x86_64 available yet, and a lib32 package was needed for this.

Now that we have flashplayer for both architectures, I see no side effects anymore in shipping libflashsupport-oss together with the oss package.

What do you guys think is the best way to solve this?
Comment by Greg (dolby) - Saturday, 28 February 2009, 15:21 GMT
IMO if the merging back with OSS is possible it sounds best, as long as it works OFC.
But this overall issue is more complex than it seems.
When community gets included in devtools, the sources of all GPLed projects,like this one, will be available in an ftp dir to solve  FS#5355 .
The *ideal* would be to solve the GPL compliance issue with giving a bit more attention to ABS.
I mean if Arch already hosts the sources, theres no reason for ABS to not work for OSS, because the developers replaced build1050 from their ftp with buil1051 and the maintainer of the package hasnt still upgraded it.
Right now, sources like that, would be saved in another dir in ftp.archlinux.org/other according to phrakture (see http://bugs.archlinux.org/task/5355#comment40380 and downwards).
But that means sources for OSS, and all other similar projects, if the PKGBUILD points to the ftp.archlinux.org/other dir will be hosted twice. I dont know how much of a problem than can be in the long run.
It probably will. And its not easy to solve.
Comment by Paulo Matias (thotypous) - Saturday, 07 March 2009, 18:05 GMT
So I'm planning to merge libflashsupport-oss in the next oss package update. Thanks.

Loading...