Skip to content

[Bioc-devel] package devel page not available

4 messages · Martin Morgan, Ludwig Geistlinger

Ludwig Geistlinger
# 
Hi,

I am trying to access the devel page of my package

https://www.bioconductor.org/packages/devel/bioc/html/EnrichmentBrowser.html

but I am obtaining

Page Not Found
The page you were looking for was not found.

What is the reason for that?

Thx,
Ludwig
Martin Morgan
#
On 07/18/2016 04:27 AM, Ludwig Geistlinger wrote:
it (has always?) failed to build in devel

http://bioconductor.org/checkResults/3.4/bioc-LATEST/EnrichmentBrowser/

because neaGUI is one of the 17 packages marked as deprecated (the 
package was not building and the author did not respond to email) in 
release 3.3 for removal in 3.4.

Martin
This email message may contain legally privileged and/or...{{dropped:2}}
Ludwig Geistlinger
# 
Thx Martin, I've missed that.

BTW: Is there a best practice for incorporating packages that are not
maintained anymore?

Am I supposed to copy the part of the discontinued package I am building
on and include that in my package? Or am I able to somehow import from an
archived version of the package?

Thx,
Ludwig

  
    

      
      
    

  


  


      

    

    

      
      

        


  

        

      Martin Morgan
    

    

      
      #
    

  


  

      
On 07/18/2016 10:10 AM, Ludwig Geistlinger wrote:

            

      
      
      
    

        
the package will not be available to your users so you must act as 
though it does not exist.

One option would be to adopt the package yourself (ideally after seeking 
consent of the original authors, but I believe they did not respond to 
earlier email).

Another option would be to break out the generally useful functionality 
of the package into a new package, and make it available through 
Bioconductor.

The least favorable but perhaps easiest is to copy the desired code.

All of these options need to be pursued within the context of the 
original license, in this case GPL-2. For copied code this includes 
clearly marking the changes and distributing your package under GPL-2.

Martin

            

      
      
      
    

        
This email message may contain legally privileged and/or...{{dropped:2}}