© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
discussion from irc on the link cleanup:
12:00 < asac> fta2: actually there is one major thing we might wanna look into
12:00 < asac> even though it scares me a bit and i am not sure if its too high risk
12:01 < asac> (flash)
12:01 < fta2> ?
12:01 < asac> the actual binary should be linked to /usr/share/
12:01 < asac> which sounds simple, but since we have two different locations we cannot use dh_link
12:01 < asac> imo we should look into fixing the fact that flash has two different locations
12:02 < asac> by lets say making whatever binary is used available in /var/lib/
12:02 < asac> which would be a link to the i386 binary on 386 and to the npviewer thing on amd64
12:02 < asac> would basically add a another link layer to the solution :(
12:08 < asac> fta2: so what we currently have is:
12:08 < asac> /usr/lib/
12:09 < asac> <= /usr/lib/
12:09 < asac> and
12:09 < asac> /usr/lib/
12:09 < asac> <= (loaded) /var/lib/
12:09 < asac> <= /usr/lib/
12:09 < asac> thats really ugly
12:09 < asac> i mean the alternative system surely shouldnt be used for doing arch dependent locations
12:10 < asac> and because of that ignorance we have the mess now
12:10 < asac> so the clean solution (please give better ideas if you have) would be:
12:10 < asac> /usr/lib/
12:10 < asac> <= /var/lib/
12:10 < asac> <= /usr/lib/
12:10 < asac> and
12:10 < asac> /usr/lib/
12:11 < asac> <= (loaded) /var/lib/
12:11 < asac> <= /var/lib/
12:11 < asac> <= /usr/lib/
12:12 < asac> (and) /var/lib/