Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 59902
Alias:
Product:
Component:
Status: RESOLVED
Resolution: WONTFIX
Assigned To: Portage team <dev-portage@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Danny van Dyk (RETIRED) <kugelfang@gentoo.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
repoman-epatchcheck.diff Patch for repoman to check epatch lines patch Danny van Dyk (RETIRED) 2004-08-09 15:05 0000 3.16 KB Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 59902 depends on: Show dependency tree
Bug 59902 blocks: 60345
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-08-09 14:56 0000 

    

  

        

        
          ------- Comment
          
            #1 From 
          Brian Harring
          2004-08-09 15:02:28 0000 
          
          
          -------
        
        



err... kugelfang?


    

  

        

        
          ------- Comment
          
            #2 From 
          Danny van Dyk (RETIRED)
          2004-08-09 15:05:05 0000 
          
          
          -------
        
        



Created an attachment (id=37123) [details]
Patch for repoman to check epatch lines

[Sorry, the keyboard has fallen down :-/, here goes the real "bug"]

Anyway: I already talked w/ jstubbs about this patch, it allows repoman to
check
all occurences of epatch in an ebuild. If it detects env. variables in the
argument to epatch,  it resolves them. (not all, up to now only FILESDIR, P,
PV,
PN) If the patchfile is not found in at its place, repoman fails with
"epatch.missing".  If there are variables in epatch which are unknown to
repoman, it still raises a warning (epatch.unknown).

I'd really like to have this function in portage, as ppl who do version bumps
sometimes just overlook arch dependent epatch lines :-/ This shouldn't happen
anymore with this patch in repoman.

    

  

        

        
          ------- Comment
          
            #3 From 
          Danny van Dyk (RETIRED)
          2004-08-09 15:06:19 0000 
          
          
          -------
        
        



Brian: was an accident, i just had opened the form, and the keyboard fell down.
Shit happens ;-)


    

  

        

        
          ------- Comment
          
            #4 From 
          Danny van Dyk (RETIRED)
          2004-08-14 15:36:34 0000 
          
          
          -------
        
        



Seems this patch needs some loving. (BUG #60345)

For example the line in comment #11 would be nice to be recognized.

Brian: do you have any idea how to accomplish that ?

    

  

        

        
          ------- Comment
          
            #5 From 
          Brian Harring
          2005-02-28 00:52:26 0000 
          
          
          -------
        
        



Whatever happened with this check... and anyone up for trying to get it going
again?


    

  

        

        
          ------- Comment
          
            #6 From 
          Alec Warner
          2006-01-25 22:17:41 0000 
          
          
          -------
        
        



Personally I think this is kinda messy, although most of epatch's are standard
vars (FILESDIR, P,PV), I would hope that the arch teams/AT's will find crap
like this before it hits the stable tree.


    

  

        

        
          ------- Comment
          
            #7 From 
          Marius Mauch (RETIRED)
          2007-01-10 06:42:03 0000 
          
          
          -------
        
        



Too many false positives to be usable. Reopen in case you have a better
version.


    







Bug List:


      (This bug is not in your last search results)

    Show last search results

     Search page
     Enter new bug