Re: man types.h
On 18/01/13 14:57, Colin Watson wrote: On Thu, Jan 17, 2013 at 02:05:47PM +0100, Lanoxx wrote: On 17/01/13 13:40, Oliver Grawert wrote: Am Donnerstag, den 17.01.2013, 13:11 +0100 schrieb Lanoxx: it seems that for solaris there exists a man page for types.h [1] but I could not find such a man page on ubuntu. Could someone give me a hint, why it does not exist or is the man page name just different on ubuntu? the manpage for types.h is in the manpages-posix-dev package, note that we dont install devleoper documentation by default ... Thanks, that was what I was looking for. Maybe you can make manpages-dev recommend this package, so it is automatically installed if developer manpages are installed? The one in manpages-posix-dev is not really quite the same. What that documents is what POSIX guarantees of , not what the system provides; so it won't tell you about any system-specific extensions, some of which might be very important to you (e.g. large file support). I think manpages-posix(-dev) are useful packages and I'm glad they exist; but I also think they should only be installed when people explicitly ask for them, because it's quite easy to miss the fact that you're looking at a manual page which documents POSIX guarantees rather than your actual system. I see you point. Thank you for the explanation. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Improving Access to Themes etc.
On Fri, Jan 18, 2013 at 4:02 PM, Vesa Paatero wrote: >By using the normal settings programs to configure the desktop, I could > only see four themes to select from, two of which were high-contrast themes > and the other two being Ubuntu themes with orange activation colors. So, the > choices we narrow, there were not really > any different styles to select from. Do you make the same complaints to Apple and Microsoft? >As I couldn't find a better solution then, I went to tamper with the > color settings of GTK and, after some late evenings' work, managed to > eradicate the oranges and bring about a satisfying look & feel. > > It seems that crux of the matter is not so much a lack of themes because > there are some themes available in the repositories (using e.g. Synaptic) > and a lot more on some GTK or Gnome-related web pages. It is more about how > to make the themes accessible to Ubuntu users, especially > new users some of which might just go away if they can't change the default > color scheme reasonably soon. > > What I suggest is adding some theme packs to Ubuntu Software Centre. > It already has a category called something like "Themes and Customizations", > but it seems not to contain any packages with desktop themes. > Another possibility would be to add some sort of "Welcome to Ubuntu" > window when you first boot Ubuntu, giving helpful links to some basic things > such as setting your default browser, finding the applications you want and > changing your desktop theme. There are already tons of themes in the repository here is a quick grep: murrine-themes gtk-clearlooks-gperfection2-theme gtk-smooth-themes Not to mention http://browse.deviantart.com/?q=unity+themes It's simple to install a theme on Linux, open up your home folder, create a .theme folder and start adding themes and then select them from the theme selector. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Improving Access to Themes etc.
Hello, I upgraded to Edubuntu 12.04 recently and encountered the following shortcoming regarding desktop themes: By using the normal settings programs to configure the desktop, I could only see four themes to select from, two of which were high-contrast themes and the other two being Ubuntu themes with orange activation colors. So, the choices we narrow, there were not really any different styles to select from. As I couldn't find a better solution then, I went to tamper with the color settings of GTK and, after some late evenings' work, managed to eradicate the oranges and bring about a satisfying look & feel. It seems that crux of the matter is not so much a lack of themes because there are some themes available in the repositories (using e.g. Synaptic) and a lot more on some GTK or Gnome-related web pages. It is more about how to make the themes accessible to Ubuntu users, especially new users some of which might just go away if they can't change the default color scheme reasonably soon. What I suggest is adding some theme packs to Ubuntu Software Centre. It already has a category called something like "Themes and Customizations", but it seems not to contain any packages with desktop themes. Another possibility would be to add some sort of "Welcome to Ubuntu" window when you first boot Ubuntu, giving helpful links to some basic things such as setting your default browser, finding the applications you want and changing your desktop theme. Thanks for considering these ideas, Vesa -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Launchpad translations for a package
I'm working on a program that will open a web browser and show the translations for a package in Launchpad. What is the best URL to go to given the package name? I've tried using https://translations.launchpad.net/ubuntu//+source/, but for the packages I've looked at, translations are managed by the Launchpad project, not the package. Should I still just show the user the package's translations page, should I try extracting the "Sharing translations with" link and show that, or is there a better way to do this? Thank you, -- Michael Spencer If thou shalt confess with thy mouth the Lord Jesus, and shalt believe in thine heart that God hath raised him from the dead, thou shalt be saved. - Romans 10:9 Whatsoever ye do in word or deed, do all in the name of the Lord Jesus, giving thanks to God and the Father by him. - Colossians 3:17 -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Discovering the package of an open window
On 01/18/2013 01:07 PM, Colin Watson wrote: > On Fri, Jan 18, 2013 at 11:32:16AM -0600, Michael Spencer wrote: >> Okay, that makes sense. What I'm trying to do is identify the package >> and then access the Launchpad entry for the package. But for example, >> Libreoffice seems to lump all the libreoffice packages into one >> Launchpad entry, https://launchpad.net/ubuntu/+source/libreoffice. Is >> there an easy way to find the Launchpad entry for a particular package? > Launchpad generally organises binary packages (e.g. libreoffice-core, > etc.) by the source package that built them (e.g. libreoffice). The > Package: line of 'apt-cache showsrc BINARY-PACKAGE-NAME' shows you the > source package name. > Perfect! Thank you! -- Michael Spencer If thou shalt confess with thy mouth the Lord Jesus, and shalt believe in thine heart that God hath raised him from the dead, thou shalt be saved. - Romans 10:9 Whatsoever ye do in word or deed, do all in the name of the Lord Jesus, giving thanks to God and the Father by him. - Colossians 3:17 -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Discovering the package of an open window
On Fri, Jan 18, 2013 at 11:32:16AM -0600, Michael Spencer wrote: > Okay, that makes sense. What I'm trying to do is identify the package > and then access the Launchpad entry for the package. But for example, > Libreoffice seems to lump all the libreoffice packages into one > Launchpad entry, https://launchpad.net/ubuntu/+source/libreoffice. Is > there an easy way to find the Launchpad entry for a particular package? Launchpad generally organises binary packages (e.g. libreoffice-core, etc.) by the source package that built them (e.g. libreoffice). The Package: line of 'apt-cache showsrc BINARY-PACKAGE-NAME' shows you the source package name. -- Colin Watson [cjwat...@ubuntu.com] -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Discovering the package of an open window
On 01/18/2013 10:54 AM, Martin Pitt wrote: > Michael Spencer [2013-01-18 10:39 -0600]: >> What is the best way to discover the package a program is in by clicking >> on an open window? >> >> So far I've been using xprop to get the PID of the window, reading where >> /proc//exe points too, and then running apt-file search on that. > That's by and large how I do it, although dpkg -S /path/to/program > doesn't require apt-file to be installed. > >> However, for some programs, like LibreOffice Writer, I get >> libreoffice-core, not libreoffice-writer. > That's actually correct. LibreOffice is really by and large one big > binary with different "modes" for Writer, etc., and it is indeedn > libreoffice-core which ships /usr/lib/libreoffice/program/soffice.bin. > > Martin > Okay, that makes sense. What I'm trying to do is identify the package and then access the Launchpad entry for the package. But for example, Libreoffice seems to lump all the libreoffice packages into one Launchpad entry, https://launchpad.net/ubuntu/+source/libreoffice. Is there an easy way to find the Launchpad entry for a particular package? Thanks, -- Michael Spencer If thou shalt confess with thy mouth the Lord Jesus, and shalt believe in thine heart that God hath raised him from the dead, thou shalt be saved. - Romans 10:9 Whatsoever ye do in word or deed, do all in the name of the Lord Jesus, giving thanks to God and the Father by him. - Colossians 3:17 -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Discovering the package of an open window
Michael Spencer [2013-01-18 10:39 -0600]: > What is the best way to discover the package a program is in by clicking > on an open window? > > So far I've been using xprop to get the PID of the window, reading where > /proc//exe points too, and then running apt-file search on that. That's by and large how I do it, although dpkg -S /path/to/program doesn't require apt-file to be installed. > However, for some programs, like LibreOffice Writer, I get > libreoffice-core, not libreoffice-writer. That's actually correct. LibreOffice is really by and large one big binary with different "modes" for Writer, etc., and it is indeedn libreoffice-core which ships /usr/lib/libreoffice/program/soffice.bin. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Discovering the package of an open window
On 18 January 2013 16:39, Michael Spencer wrote: > What is the best way to discover the package a program is in by clicking > on an open window? > > So far I've been using xprop to get the PID of the window, reading where > /proc//exe points too, and then running apt-file search on that. > > However, for some programs, like LibreOffice Writer, I get > libreoffice-core, not libreoffice-writer. > > For the program I'm writing, Contributor Console (written in python), > the executable is /usr/bin/python2.7, even though I launched it with the > command contributor-console. > > So, what is the best way to accurately discover the package a program is > in by clicking on an open window? > I have a really crappy program that already does this at: https://launchpad.net/start-hacking A quick look at the code should answer your question. cheers, jml -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Discovering the package of an open window
What is the best way to discover the package a program is in by clicking on an open window? So far I've been using xprop to get the PID of the window, reading where /proc//exe points too, and then running apt-file search on that. However, for some programs, like LibreOffice Writer, I get libreoffice-core, not libreoffice-writer. For the program I'm writing, Contributor Console (written in python), the executable is /usr/bin/python2.7, even though I launched it with the command contributor-console. So, what is the best way to accurately discover the package a program is in by clicking on an open window? Thank you, -- Michael Spencer If thou shalt confess with thy mouth the Lord Jesus, and shalt believe in thine heart that God hath raised him from the dead, thou shalt be saved. - Romans 10:9 Whatsoever ye do in word or deed, do all in the name of the Lord Jesus, giving thanks to God and the Father by him. - Colossians 3:17 -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
error in upgrade to 12.04 (64 bit) from 11.10 (64 bit) using wubi as installer
I happen to get some failure in doing a 11.04 to 12.04 move so I stuck back to Wubi here is my message on user list https://lists.ubuntu.com/archives/ubuntu-users/2013-January/266972.html how ever it appears the ability to install using wubi has been disabled as mentioned on this message https://lists.ubuntu.com/archives/ubuntu-devel/2012-March/034970.html please let me know if there is a situation for people like me on Windows 7. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: man types.h
On Thu, Jan 17, 2013 at 02:05:47PM +0100, Lanoxx wrote: > On 17/01/13 13:40, Oliver Grawert wrote: > >Am Donnerstag, den 17.01.2013, 13:11 +0100 schrieb Lanoxx: > >>it seems that for solaris there exists a man page for types.h [1] but I > >>could not find such a man page on ubuntu. Could someone give me a hint, > >>why it does not exist or is the man page name just different on ubuntu? > > > >the manpage for types.h is in the manpages-posix-dev package, note that > >we dont install devleoper documentation by default ... > > Thanks, that was what I was looking for. Maybe you can make > manpages-dev recommend this package, so it is automatically > installed if developer manpages are installed? The one in manpages-posix-dev is not really quite the same. What that documents is what POSIX guarantees of , not what the system provides; so it won't tell you about any system-specific extensions, some of which might be very important to you (e.g. large file support). I think manpages-posix(-dev) are useful packages and I'm glad they exist; but I also think they should only be installed when people explicitly ask for them, because it's quite easy to miss the fact that you're looking at a manual page which documents POSIX guarantees rather than your actual system. -- Colin Watson [cjwat...@ubuntu.com] -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
