| View previous topic :: View next topic |
| Author |
Message |
randalla
Tux's lil' helper
Joined: 14 Oct 2008
Posts: 79
Location: Seattle, WA
|
 Posted: Fri Jan 04, 2013 12:23 am Post subject: Help: compiling libgxps from GIT master and installing |
 |
|
I would appreciate a little help if possible. I've been asked by the maintainer of libgxps to test the most recent change to the source which has support for interleaved XPS documents. All I want to do is uninstall the existing libgxps on my development box, compile the source from the GIT master, and get it installed for testing. Is it possible to use an overlay for this (something that I've not actually used)? Or should I just compile this directly and install it somewhere like /opt?
Alternately, if someone else wants to try this I can give you demo interleaved XPS documents.
Adam. |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 21908
|
| Posted: Fri Jan 04, 2013 2:59 am Post subject: |
|
|
| An overlay can let you do this, especially if the recent change can be applied cleanly on a version already available in Portage. I strongly suggest that you do not perform a manual install, since that can be difficult to remove later. Can you post a link to the patch, ideally as the commit in Gitweb or similar viewer? This will allow us to evaluate how closely the current tip code resembles a version in Portage. |
|
| Back to top |
|
|
randalla
Tux's lil' helper
Joined: 14 Oct 2008
Posts: 79
Location: Seattle, WA
|
| Posted: Fri Jan 04, 2013 5:56 am Post subject: |
|
|
| Hu wrote: | | An overlay can let you do this, especially if the recent change can be applied cleanly on a version already available in Portage. I strongly suggest that you do not perform a manual install, since that can be difficult to remove later. Can you post a link to the patch, ideally as the commit in Gitweb or similar viewer? This will allow us to evaluate how closely the current tip code resembles a version in Portage. |
It is located here: http://git.gnome.org/browse/libgxps (the three that are 14 days old).
It looks to be a very minor amount of code changed.
I'm really under the weather here, so my responses are slow please be patient with me  |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 21908
|
| Posted: Fri Jan 04, 2013 11:39 pm Post subject: |
|
|
| The number of commits is small, so if you only need to test once, I suggest exporting the current Git HEAD, copying the ebuild to an overlay, and changing its SRC_URI to reference the exported HEAD. If you need more detail, ask. |
|
| Back to top |
|
|
randalla
Tux's lil' helper
Joined: 14 Oct 2008
Posts: 79
Location: Seattle, WA
|
| Posted: Fri Jan 04, 2013 11:41 pm Post subject: |
|
|
| Hu wrote: | | The number of commits is small, so if you only need to test once, I suggest exporting the current Git HEAD, copying the ebuild to an overlay, and changing its SRC_URI to reference the exported HEAD. If you need more detail, ask. |
I'll see what I can do
Adam. |
|
| Back to top |
|
|
|
Portage & Programming
